00:25:56  * BridgeARquit (Ping timeout: 246 seconds)
02:03:58  * joaocgreisquit (Ping timeout: 240 seconds)
02:04:09  * joaocgreisjoined
02:17:29  * Fishrock123joined
02:35:31  * node-ghjoined
02:35:32  * node-ghpart
04:09:50  * Fishrock123quit (Remote host closed the connection)
04:38:46  * ryzokukenjoined
04:51:24  * Fishrock123joined
05:06:37  * Fishrock123quit (Remote host closed the connection)
05:26:56  * juggernaut451joined
05:36:12  * Fishrock123joined
05:51:42  * Fishrock123quit (Remote host closed the connection)
05:55:02  * Fishrock123joined
06:12:49  * Fishrock123quit (Remote host closed the connection)
06:14:33  * seishunjoined
06:42:10  * Fishrock123joined
06:44:42  * Fishrock123quit (Client Quit)
07:19:08  * ryzokukenquit (Remote host closed the connection)
07:34:27  * seishunquit (Ping timeout: 240 seconds)
08:07:54  * BridgeARjoined
10:25:08  * mylesborinsquit (Quit: farewell for now)
10:25:38  * mylesborinsjoined
12:37:02  * ryzokukenjoined
13:15:27  * node-ghjoined
13:15:27  * node-ghpart
13:24:15  * node-ghjoined
13:24:15  * node-ghpart
13:30:28  * juggernaut451quit (Remote host closed the connection)
14:02:35  * juggernaut451joined
14:04:30  * juggernaut451quit (Read error: Connection reset by peer)
16:05:13  * juggernaut451joined
16:07:02  * juggernaut451quit (Remote host closed the connection)
16:28:11  * juggernaut451joined
16:36:24  * seishunjoined
17:36:15  <addaleax>something up with the windows machines? https://ci.nodejs.org/job/node-test-commit/18338/
17:37:45  <refack>checking it out
17:38:36  <addaleax>thanks :)
17:48:20  * juggernaut451quit (Remote host closed the connection)
17:48:54  * juggernaut451joined
17:53:08  * juggernaut451quit (Ping timeout: 246 seconds)
18:21:14  * seishunquit (Ping timeout: 260 seconds)
18:34:27  * seishunjoined
20:14:15  * seishunquit (Ping timeout: 256 seconds)
20:26:08  * seishunjoined
20:31:06  * seishunquit (Ping timeout: 255 seconds)
20:45:58  <ryzokuken>It seems to be fixed
20:46:13  <ryzokuken>but I'm still getting way too many Java errors (just now: https://ci.nodejs.org/job/node-test-commit-freebsd/17632/nodes=freebsd10-64/console)
20:46:30  <ryzokuken>https://github.com/nodejs/node/pull/19898 is getting impossible to test
20:57:54  <refack>ryzokuken: this one is unusual.
20:58:19  <ryzokuken>the failure?
20:58:38  <ryzokuken>I hope there's nothing amiss with the PR, the failure seems unrelated to the code.
20:58:38  <refack>yes, it seems like the server crashed
20:58:48  <ryzokuken>perhaps something wrong with the infra?
20:59:01  <ryzokuken>yes, something of the sort was what I had been thinking about.
20:59:20  <ryzokuken>refack could you please investigate whenever you had the time to?
21:00:32  <refack>we have duplicate servers for every platform, so a new job should be able proceed - https://ci.nodejs.org/job/node-test-commit-freebsd/17633/
21:00:59  <refack>Meanwhile I'm looking if I can revive the other server
21:08:36  <ryzokuken>refack https://ci.nodejs.org/job/node-test-commit-linux/nodes=ubuntu1604-32/18614/console failed too
21:08:53  <ryzokuken>`make[1]: *** wait: No child processes. Stop.`
21:11:36  <refack>The actual fail is a timeout
21:11:40  <refack>https://www.irccloud.com/pastebin/GsYZvpkN/
21:11:45  <refack>might be related?
21:12:45  * seishunjoined
21:19:15  <ryzokuken>refack I don't believe my PR should cause the build to take that long, so no.
21:20:04  <refack>that line is a call to the compiled node binary to generate the docs
21:23:09  <ryzokuken>oh, the docs were changed, but again nothing that would delay the build
21:26:57  * seishunquit (Ping timeout: 240 seconds)