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
13:53:55  * seishunjoined
13:55:21  * starefossenquit (Ping timeout: 255 seconds)
13:57:04  * starefossenjoined
13:57:26  * othiym23quit (Ping timeout: 255 seconds)
13:59:31  * othiym23joined
14:03:17  * mmarchiniquit (Ping timeout: 255 seconds)
14:03:24  * mmarchinijoined
14:39:36  <Trott>rvagg: They're not showing up in the Jenkins interface after many hours though.
14:39:52  <Trott>https://ci.nodejs.org/job/node-stress-single-test-pi1-fanned/ stops at job 70.
14:58:01  * node-ghjoined
14:58:01  * node-ghpart
15:04:02  * node-ghjoined
15:04:02  * node-ghpart
15:20:54  * BridgeARjoined
15:23:25  * evanluca_changed nick to evanlucas
16:57:24  * Fishrock123joined
17:14:09  * sgimenoquit (Ping timeout: 276 seconds)
17:15:47  * sgimenojoined
17:32:29  * BridgeARquit (Ping timeout: 268 seconds)
18:09:26  <Trott>Who was it on build that took care of 2FA for the bots?
18:11:06  <Trott>Whoever it was, can you please head over to https://github.com/nodejs/community-committee/issues/247 and provide some guidance? :-D
18:55:06  * BridgeARjoined
19:07:49  * Fishrock123quit (Remote host closed the connection)
19:16:49  * Fishrock123joined
19:17:02  * Fishrock123quit (Remote host closed the connection)
19:19:29  * BridgeARquit (Ping timeout: 248 seconds)
19:23:07  * BridgeARjoined
19:33:47  * Fishrock123joined
19:51:10  * BridgeARquit (Remote host closed the connection)
21:51:05  * seishunquit (Ping timeout: 240 seconds)
22:15:39  * evanlucasquit (Remote host closed the connection)
22:41:45  <rvagg>Trott: yeah .. so all your jobs show up when you go to them directly, e.g. https://ci.nodejs.org/job/node-stress-single-test-pi1-fanned/73/, but they're missing from the parent job listing and I have no idea why! this is one of those quirks of jenkins that has become increasingly annoying, in fact it seems have become increasingly common.
22:42:08  <rvagg>Trott: my only guess, if we were to take blame, is that it could be related to our backup and history-trimming scripts that also force a jenkins config reload every day
22:42:29  <rvagg>maybe it's time to find a plugin to do history trimming rather than doing it externally
22:48:51  * seishunjoined
22:59:45  * seishunquit (Ping timeout: 264 seconds)
23:09:57  * BridgeARjoined
23:51:10  * BridgeARquit (Quit: WeeChat 2.0.1)
23:51:54  * Fishrock123quit (Quit: Leaving...)