00:07:57  * node-ghjoined
00:07:57  * node-ghpart
00:26:52  * joyeejoined
00:31:05  * joyeequit (Ping timeout: 240 seconds)
00:32:06  * node-ghjoined
00:32:06  * node-ghpart
00:57:54  * Fishrock123quit (Remote host closed the connection)
01:03:28  * joyeejoined
01:04:03  * node-ghjoined
01:04:03  * node-ghpart
01:07:45  * joyeequit (Ping timeout: 248 seconds)
01:17:29  * Fishrock123joined
01:22:42  * Fishrock123quit (Ping timeout: 260 seconds)
01:41:16  * node-ghjoined
01:41:16  * node-ghpart
02:02:24  * joyeejoined
02:29:26  * node-ghjoined
02:29:26  * node-ghpart
02:45:33  * node-ghjoined
02:45:33  * node-ghpart
03:00:47  * node-ghjoined
03:00:47  * node-ghpart
05:12:08  * joyeequit
05:15:21  <Trott>Anybody know what's up with the stalled-ness going on with CI? https://ci.nodejs.org/job/node-test-pull-request/10661/ started 49 minutes ago but still hasn't started the node-test-commit subtask. Neither have any of the six node-test-pull-request tasks that have been started since then.
05:37:52  <Trott>And now they've all gone green but haven't run any tests. I left comments in all the PRs letting people know CI needs to be re-run. But uh, not sure if someone on build needs to do something to fix it before it will start working again....
05:38:31  <Trott>Most recent node-test-pull-request run as of now is https://ci.nodejs.org/job/node-test-pull-request/10668/ and it shows the problem. If any more happen after that, someone (coudl be me, but could be you!) will have to leave a comment in the affected PRs, I guess.
05:40:10  * sgimeno_changed nick to sgimeno
08:13:39  * node-ghjoined
08:13:39  * node-ghpart
09:33:52  * sgimeno_joined
09:36:33  * sgimenoquit (Ping timeout: 258 seconds)
09:53:15  * node-ghjoined
09:53:15  * node-ghpart
10:03:42  * seishunjoined
10:25:12  * mylesborinsquit (Quit: farewell for now)
10:25:42  * mylesborinsjoined
10:27:44  * sgimeno_changed nick to sgimeno
10:35:57  * seishunquit (Quit: Leaving)
10:36:26  * seishunjoined
12:18:31  * seishunquit (Remote host closed the connection)
12:19:15  * seishunjoined
13:53:27  <joaocgreis>Trott: Jenkins being Jenkins. Thanks for the warning! Let me see what I can do
14:18:41  <joaocgreis>I think I have it figured out. https://github.com/nodejs/build/issues/265 got fixed by the Jenkins update, but still needs some changes in some jobs. I'm looking at it
14:20:20  * node-ghjoined
14:20:20  * node-ghpart
14:41:32  * node-ghjoined
14:41:32  * node-ghpart
14:44:47  * node-ghjoined
14:44:47  * node-ghpart
14:45:27  * node-ghjoined
14:45:27  * node-ghpart
15:58:28  * node-ghjoined
15:58:28  * node-ghpart
16:29:12  * node-ghjoined
16:29:12  * node-ghpart
16:43:23  * node-ghjoined
16:43:23  * node-ghpart
17:23:57  * seishunquit (Ping timeout: 240 seconds)
17:38:07  <tniessen>Could someone explain this to me? Why are there no subtasks? https://ci.nodejs.org/job/node-test-pull-request/10676/
17:40:17  <refack>Trott raised this issue 12 hours ago. I think Joao fixed it 3 hour ago
17:47:29  * seishunjoined
18:22:23  <tniessen>refack: thanks, tried to restart it but running into gateway timeouts
18:25:50  * gibfahnjoined
19:18:43  * node-ghjoined
19:18:43  * node-ghpart
19:20:02  * node-ghjoined
19:20:02  * node-ghpart
19:22:28  * node-ghjoined
19:22:28  * node-ghpart
20:05:30  * node-ghjoined
20:05:30  * node-ghpart
20:05:49  * node-ghjoined
20:05:49  * node-ghpart
20:32:46  * seishunquit (Ping timeout: 264 seconds)
20:56:24  * evanlucasquit (Remote host closed the connection)
21:09:12  * seishunjoined
21:10:45  * jasnelljoined
21:11:17  <jasnell>Ping Build Folk... https://ci.nodejs.org/job/node-test-binary-arm/10874/ looks like one of the arm wheezy bots is dead
21:11:21  <jasnell>failing consistently
21:44:12  * seishunquit (Ping timeout: 260 seconds)
22:05:35  * gibfahnquit (Quit: Connection closed for inactivity)
23:17:34  * Fishrock123joined