00:29:25  * Guest72457changed nick to indutny
01:01:09  * node-ghjoined
01:01:09  * node-ghpart
10:02:03  * seishunjoined
10:46:37  * seishunquit (Read error: Connection reset by peer)
10:53:42  * seishunjoined
10:59:49  * seishunquit (Ping timeout: 256 seconds)
11:08:00  * seishunjoined
11:11:29  <rvagg>had to restart the softlayer docker machine, would have disrupted some jobs running there, I saw alpine jobs at least
11:11:46  <rvagg>sorry if anyone in here owns them .. machine had some serious problems that needed action
11:23:30  <rvagg>FYI test-packetnet-ubuntu1604-x64-1 dropped out of the universe ... not sure what packet.net did with it but I'm provisioning a new one. This is a jenkins-workspace machine.
11:23:31  <rvagg> We had problems with both of the packet.net ones earlier today and I repaired them but now this one is gone.
11:24:54  * node-ghjoined
11:24:54  * node-ghpart
11:25:11  * mylesborinsquit (Quit: farewell for now)
11:25:47  * mylesborinsjoined
11:37:18  * node-ghjoined
11:37:18  * node-ghpart
11:38:37  * node-ghjoined
11:38:37  * node-ghpart
11:40:13  * node-ghjoined
11:40:13  * node-ghpart
11:42:28  * node-ghjoined
11:42:28  * node-ghpart
11:43:13  * node-ghjoined
11:43:13  * node-ghpart
14:05:42  * node-ghjoined
14:05:42  * node-ghpart
14:24:15  * chorrelljoined
14:51:46  * seishunquit (Ping timeout: 248 seconds)
15:36:34  * Fishrock123joined
15:55:45  * seishunjoined
16:03:30  * BridgeARjoined
16:27:55  * BridgeARquit (Ping timeout: 256 seconds)
16:29:51  * BridgeARjoined
16:41:02  * node-ghjoined
16:41:02  * node-ghpart
16:43:18  * node-ghjoined
16:43:18  * node-ghpart
17:10:57  * BridgeARquit (Ping timeout: 248 seconds)
17:18:44  * node-ghjoined
17:18:44  * node-ghpart
17:42:21  * seishunquit (Ping timeout: 276 seconds)
17:49:32  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:25:39  * Fishrock123quit (Remote host closed the connection)
18:32:06  * Fishrock123joined
18:49:03  * node-ghjoined
18:49:03  * node-ghpart
18:54:37  * srl295joined
19:01:32  * chorrelljoined
19:06:24  * node-ghjoined
19:06:24  * node-ghpart
19:30:21  * node-ghjoined
19:30:21  * node-ghpart
19:33:23  * node-ghjoined
19:33:23  * node-ghpart
19:33:44  * node-ghjoined
19:33:45  * node-ghpart
19:52:00  * node-ghjoined
19:52:00  * node-ghpart
19:56:22  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:58:04  * chorrelljoined
20:06:12  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
20:39:23  * node-ghjoined
20:39:23  * node-ghpart
20:56:29  * node-ghjoined
20:56:30  * node-ghpart
22:10:39  * seishunjoined
23:03:23  * node-ghjoined
23:03:23  * node-ghpart
23:12:31  * seishunquit (Ping timeout: 248 seconds)
23:31:29  <rvagg>mylesborins: I've started a second release build https://ci-release.nodejs.org/job/iojs+release/3033/ and cancelled most of the builders leaving the pi1. Your build picked the mhdawson Pi which has been successfully building for some time, it just hangs. I've marked it offline for now and the 3033 build should spit out a binary for you (eventually).
23:49:21  * Fishrock123quit (Quit: Leaving...)
23:55:56  <rvagg>ok, so it turns out the current version of iojs+build is ignoring $JOBS in many of the cases ... that's annoying cause I've tried to force JOBS=1 for the Pi's to stop overload but they've been running at a fixed JOBS=2
23:56:06  <rvagg>so I've fixed it all up to respect JOBS and if JOBS isn't set then use 2
23:56:23  <rvagg>could explain some of the release Pi instability I've been so frustrated about