03:02:56  <refack>Well the coverage job doesn't fail. Still need to make sure it tests "internet", and publishes as usual...
04:18:01  * node-slack-botpart
04:21:22  * node-slack-botjoined
04:22:55  * node-slack-botquit (Remote host closed the connection)
04:24:10  * node-slack-botjoined
05:04:16  * node-ghjoined
05:04:16  * node-ghpart
05:08:19  <node-slack-bot>[trott] Sure looks like it. Compare https://coverage.nodejs.org/coverage-3bdc61d4d194e205/root/internal/dns/promises.js.html to the run from 24 hours before at https://coverage.nodejs.org/coverage-9782ce25750f2a34/root/internal/dns/promises.js.html.
10:21:05  * sxajoined
10:57:03  * node-ghjoined
10:57:03  * node-ghpart
15:01:19  <node-slack-bot>[george.adams] http://ci.nodejs.org appears to be down for me again
15:02:00  <node-slack-bot>[refack] refresh a couple of time :shrug4:
15:23:12  <node-slack-bot>[george.adams] seems to be back now but running incredibly slowly, has anybody got access to the CPU/memory usage on the machine?
15:33:33  <node-slack-bot>[refack] https://ci.nodejs.org/monitoring#systeminfo
15:34:47  <node-slack-bot>[refack] My guess is it's a rogue plugin
15:35:03  <node-slack-bot>[refack] Maybe it's querying all the nodes
15:35:28  <node-slack-bot>[refack] https://files.sameroom.io/YLTqsuyi7fa4YkmLOEUAVgupE_wVIlDpborO7o3eoV0/image.png
15:36:05  <refack>Ooooh pics gen nicly embedded in irccloud
15:43:24  <node-slack-bot>[george.adams] hmm let me see if any knew plugins were installed/updated
15:49:56  <node-slack-bot>[george.adams] from Michael:
15:49:56  <node-slack-bot>```the ci does show that most of its memory is used
15:49:56  <node-slack-bot>and the java process says it as 25G virtual address spaced```
15:54:50  <node-slack-bot>[matheusdot] Using that much virtual memory, maybe linux is swapping a lot?
16:53:13  <node-slack-bot>[refack] I would assume the CPU graph shows user time, swapping would be kernel time?
17:46:30  * node-ghjoined
17:46:30  * node-ghpart
18:10:14  * node-ghjoined
18:10:14  * node-ghpart
19:12:36  * sxaquit (Ping timeout: 252 seconds)
19:24:38  * node-ghjoined
19:24:39  * node-ghpart
20:00:14  * node-ghjoined
20:00:14  * node-ghpart
20:18:52  <node-slack-bot>[refack] I just went 12 rounds with Jenkins... He almost got me, but eventually I got him down. :crossed_fingers:for it continuing to behave, and be responsive
20:21:34  * benjamincoejoined
21:19:11  * benjamincoequit
21:56:52  <joaocgreis>git-rebase is not working well, I'm looking at it
21:57:02  <joaocgreis>what is node-slack-bot?
22:06:43  <node-slack-bot>[ljharb] an IRC-slack bridge
22:21:14  * node-ghjoined
22:21:14  * node-ghpart
22:21:59  <refack>joaocgreis: there were problems with the Jenkins config, WRT some plugins, so it might be there
22:22:10  * node-ghjoined
22:22:10  * node-ghpart
22:24:31  <joaocgreis>refack: thanks, that may be related. Somehow ~ was not expanding, changing the script that uses it to bash seem to have worked.
22:27:12  <joaocgreis>ljharb: thanks! Should we be on slack now? First time I read about this, please point me in the right direction if I missed a discussion somewhere
22:29:42  <ljharb>joaocgreis: you can be if you like; but you don't have to be. i think most of the convo was happening on IRC but a few folks vastly preferred slack, so this was the compromise
22:29:44  <refack>joaocgreis: we're mirroring this channel with a room on nodeslckers slack, so you can choose which one is more comfortable for you
22:30:34  <joaocgreis>:+1
22:30:55  <joaocgreis>👍 I'll stay around here then
22:31:19  * node-ghjoined
22:31:19  * node-ghpart
22:50:46  * node-ghjoined
22:50:47  * node-ghpart
22:55:57  * node-ghjoined
22:55:57  * node-ghpart
23:27:56  * node-ghjoined
23:27:56  * node-ghpart