02:55:24  * rmgquit (Remote host closed the connection)
04:04:22  * rmgjoined
04:09:06  * rmgquit (Ping timeout: 250 seconds)
05:05:05  * rmgjoined
05:09:36  * rmgquit (Ping timeout: 244 seconds)
05:19:50  * node-ghjoined
05:19:50  * node-ghpart
10:54:08  * thealphanerdquit (Quit: farewell for now)
10:54:39  * thealphanerdjoined
14:08:59  * rmgjoined
14:13:39  * rmgquit (Ping timeout: 260 seconds)
15:28:34  * Fishrock123joined
15:39:46  * rmgjoined
15:44:03  * rmgquit (Ping timeout: 240 seconds)
18:44:04  * Fishrock123quit (Quit: Leaving...)
19:18:21  * node-ghjoined
19:18:21  * node-ghpart
19:41:39  <Trott>When I see "slave went offline" like this, is it worth mentioning here or in an issue? Or only if it's happening a *lot*? Or...? https://ci.nodejs.org/job/node-test-commit-arm/2845/nodes=armv7-ubuntu1404/console
19:43:36  <Trott>Perhaps more interestingly, Raspberry Pi 2 builds look like they're blowing up a lot again: https://ci.nodejs.org/job/node-test-binary-arm/1679/RUN_SUBSET=0,nodes=pi2-raspbian-wheezy/console https://ci.nodejs.org/job/node-test-binary-arm/1679/RUN_SUBSET=1,nodes=pi2-raspbian-wheezy/console
19:43:36  <Trott>https://ci.nodejs.org/job/node-test-binary-arm/1679/RUN_SUBSET=3,nodes=pi2-raspbian-wheezy/console https://ci.nodejs.org/job/node-test-binary-arm/1679/RUN_SUBSET=4,nodes=pi2-raspbian-wheezy/console /cc rvagg
20:44:12  * Fishrock123joined
21:17:06  * node-ghjoined
21:17:06  * node-ghpart
22:27:44  * rmgjoined
22:32:37  * rmgquit (Ping timeout: 260 seconds)
23:14:53  * Fishrock123quit (Remote host closed the connection)