00:44:50  * BridgeARjoined
00:53:24  * node-ghjoined
00:53:24  * node-ghpart
01:00:05  * BridgeARquit (Ping timeout: 240 seconds)
01:02:11  * BridgeARjoined
01:24:15  * BridgeARquit (Ping timeout: 248 seconds)
04:22:50  * node-ghjoined
04:22:50  * node-ghpart
04:31:28  * node-ghjoined
04:31:28  * node-ghpart
05:19:03  * node-ghjoined
05:19:03  * node-ghpart
06:11:33  <Trott>rvagg: Can't add jobs to node-stress-single-test-pi1-fanned again. NFS issue?
06:59:22  <rvagg>Trott: I think maybe you're just impatient? I see 3 actively running https://ci.nodejs.org/job/node-stress-single-test-pi1-binary/label=pi1-raspbian-wheezy/68/ & 69 & 70 and I think there might be two more in the queue waiting to run (not sure why there's a queue, Jenkins is getting weird)
07:00:33  <rvagg>Trott: it says that https://ci.nodejs.org/job/node-stress-single-test-pi1-fanned/71/ and https://ci.nodejs.org/job/node-stress-single-test-pi1-fanned/72/ are also in the queue, or running, or something, even though there's a 404 -- go to ci.nodejs.org and look down the left side and you'll see all of these running near eachother on test-packetnet-ubuntu1604-x64-1
07:00:59  <rvagg>Trott: oh, and https://ci.nodejs.org/view/All/job/node-stress-single-test-pi1-fanned/73/ on test-softlayer-ubuntu1604-x64-1
07:01:15  <rvagg>Trott: so you have quite a few running and waiting and I don't think I see errors
10:37:34  * seishunjoined
10:49:34  * evanluca_joined
10:52:14  * evanlucasquit (Ping timeout: 264 seconds)
11:07:49  * node-ghjoined
11:07:49  * node-ghpart
11:25:12  * mylesborinsquit (Quit: farewell for now)
11:25:42  * mylesborinsjoined
12:20:57  * seishunquit (Ping timeout: 256 seconds)
12:51:17  * maclover7quit (Ping timeout: 255 seconds)
12:51:29  * maclover7joined
12:52:38  * zkatquit (Ping timeout: 255 seconds)
12:54:14  * zkatjoined