01:49:07  * chorrelljoined
01:49:16  * chorrellquit (Client Quit)
02:15:38  * jbergstroemtopic: we're the nodejs build group. https://ci.nodejs.org https://github.com/nodejs/build -- irc logs: http://logs.libuv.org/node-build/latest
02:22:42  * {slurp-nodejs}1quit (*.net *.split)
03:06:19  * Fishrock123joined
03:38:12  * Fishrock123quit (Remote host closed the connection)
03:49:53  * Fishrock123joined
05:04:42  * Fishrock123quit (Remote host closed the connection)
05:05:52  * Fishrock123joined
05:28:35  * Fishrock123quit (Remote host closed the connection)
05:28:54  * Fishrock123joined
05:29:20  * Fishrock123quit (Remote host closed the connection)
05:52:23  <Trott>I took test-requireio_securogroup-debian7-arm_pi1p-1 offline due to 21 consecutive build failures. rvagg
05:52:26  <Trott>https://www.irccloud.com/pastebin/ZzKChOmn/
05:52:59  <rvagg>Thanks Trott
06:26:40  <Trott>Anybody know what this failure is caused by?
06:26:41  <Trott>https://ci.nodejs.org/job/node-test-commit-plinux/13611/nodes=ppcle-ubuntu1404/console
06:27:15  <Trott>https://www.irccloud.com/pastebin/6qK000P9/
06:33:54  * Fishrock123joined
06:38:09  * Fishrock123quit (Ping timeout: 246 seconds)
06:44:14  * Fishrock123joined
06:48:20  <Trott>rvagg Looks like same thing may be up with test-requireio_securogroup-debian7-arm_pi1p-2. Taking it offline too.
06:48:46  <Trott>https://www.irccloud.com/pastebin/ppuAc6Yz/
06:49:39  <Trott>rvagg And test-requireio_kahwee-debian8-arm_pi3-1 as well. Yikes.
06:59:48  <Trott>rvagg And debian7-arm_pi1p-1. Taking it offline too. GOOD TIMES!!!!
07:01:39  <Trott>rvagg: Oops, that last one was test-requireio_mininodes-debian7-arm_pi1p-1. And now also test-requireio_mhdawson-debian7-arm_pi1p-1. I guess I can probably stop enumerating them and you can just look and see which ones are offline.
07:03:11  <Trott>test-requireio_chrislea-debian7-arm_pi1p-1 too
07:06:05  <Trott> test-requireio_pivotalagency-debian8-arm_pi3-2 too
07:07:45  <Trott>Well this is unfortunate. I stopped a task and now a whole bunch of them which weren't failing a few minutes ago are failing. :-(
07:10:11  <Trott>(Is there a troubleshooting doc for the Pi devices so maybe I can try to get these fixed myself when this sort of thing happens?)
07:22:12  <Trott>A rerun from scratch rather than using Rebuild seems to have fixed the recently-failing ones, so that's good.
07:32:12  * Fishrock123quit (Quit: Leaving...)
08:07:02  <Trott>Behold! Green Raspberry Pi CI. I can go to sleep now.
08:07:05  <Trott>https://ci.nodejs.org/job/node-test-binary-arm/12273/
08:43:28  * seishunjoined
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
14:31:25  * apapirovskijoined
14:49:31  * evanlucasjoined
14:49:44  * evanlucasquit (Changing host)
14:49:44  * evanlucasjoined
16:00:17  * apapirovskiquit (Remote host closed the connection)
16:05:46  * apapirovskijoined
16:07:53  * apapirovskiquit (Remote host closed the connection)
16:07:59  * apapirovskijoined
16:14:49  * apapirov_joined
16:18:09  * apapirovskiquit (Ping timeout: 248 seconds)
16:49:12  * apapirovskijoined
16:49:12  * apapirov_quit (Read error: Connection reset by peer)
16:49:19  * apapirovskiquit (Read error: Connection reset by peer)
16:58:32  * apapirovskijoined
17:02:57  * apapirovskiquit (Ping timeout: 240 seconds)
18:47:46  * node-ghjoined
18:47:46  * node-ghpart
20:10:57  * node-ghjoined
20:10:58  * node-ghpart
20:17:29  * seishunquit (Ping timeout: 276 seconds)
20:44:40  * seishunjoined
21:04:40  * apapirovskijoined
21:14:18  * apapirov_joined
21:14:18  * apapirovskiquit (Read error: Connection reset by peer)
21:23:46  * node-ghjoined
21:23:47  * node-ghpart
21:24:30  * apapirov_quit (Quit: Leaving...)
21:47:57  * node-ghjoined
21:47:57  * node-ghpart
21:49:57  * seishunquit (Ping timeout: 240 seconds)
21:49:59  * node-ghjoined
21:49:59  * node-ghpart
22:02:26  * evanlucasquit (Remote host closed the connection)
22:26:13  * node-ghjoined
22:26:13  * node-ghpart
23:39:52  * node-ghjoined
23:39:53  * node-ghpart