00:07:45  * Fishrock123joined
00:19:58  * node-ghjoined
00:19:58  * node-ghpart
00:40:37  * Fishrock123quit (Remote host closed the connection)
01:01:01  * Fishrock123joined
01:12:51  * Fishrock123quit (Remote host closed the connection)
01:24:32  <jbergstroem>mhdawson_: do we need to act on the power issues?
01:47:28  * node-ghjoined
01:47:28  * node-ghpart
01:48:25  * Fishrock123joined
01:48:32  * Fishrock123quit (Remote host closed the connection)
02:05:00  * node-ghjoined
02:05:00  * node-ghpart
02:05:11  * node-ghjoined
02:05:11  * node-ghpart
02:32:43  * Fishrock123joined
02:34:11  * Fishrock123quit (Client Quit)
04:48:13  <rvagg>cluster coming back online slowly, will be doing a bit of maintenance as well so it won't be speedy
05:18:30  <rvagg>should be good now
06:01:29  * node-ghjoined
06:01:29  * node-ghpart
06:15:37  * node-ghjoined
06:15:37  * node-ghpart
06:45:55  <rvagg>jbergstroem: I can't get in to test-rackspace-ubuntu1604-x64-1, 119.9.51.176, I'm guessing you set that one up, can you check that nodejs_build_test is in there for root? I can get in to -2 just fine
06:50:42  <rvagg>what's with these alpine OOM failures? https://ci.nodejs.org/job/node-test-commit-linux/10445/nodes=ubuntu1604_docker_alpine34-64/ has there been discussion about these yet? 2G of RAM on those so what gives?
07:21:02  * node-ghjoined
07:21:02  * node-ghpart
10:25:10  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
10:35:49  <rvagg>both release raspberry pi's are dead! what is this??
10:36:05  <rvagg>they won't boot
12:30:27  <rvagg>release machines recvering, one is building so at least there's that
12:30:37  <rvagg>the other machines however ... seem to be having serious problems with nfs
12:30:44  <rvagg>and I don't know what's going on
12:38:39  <rvagg>the pi3's, they all have some odd nfs problem
12:40:33  <rvagg>could be related to my clearing out of all of the nfs workspaces so they all have to build them up again, maybe it's simply a matter of massive parallel work and I need to be patient
12:41:35  <rvagg>doesn't explain why the pi2's are all fine, the pi1's are working but just slowly, that's expected, something really weird going on with the pi3's
12:46:24  * node-ghjoined
12:46:24  * node-ghpart
12:58:05  * node-ghjoined
12:58:05  * node-ghpart
13:08:45  <rvagg>I'm heading off to bed, still unsure wth is going on https://ci.nodejs.org/job/node-test-binary-arm/8562/
13:09:06  <rvagg>will look again tomorrow, aix release build is in process, attempting an armv6 too but the last one timed out (or something)
13:09:37  <jbergstroem>rvagg: will check ubuntu shortly
13:12:31  * node-ghjoined
13:12:31  * node-ghpart
13:13:34  * node-ghjoined
13:13:34  * node-ghpart
13:18:29  * refackjoined
13:19:02  <refack>Hi. How to I get myself one of those magical linuxone machines?
13:31:50  * 7F1ABBX6Cjoined
13:31:50  * 7F1ABBX6Cpart
13:31:50  * 17SAA8K2Ijoined
13:31:50  * 17SAA8K2Ipart
17:29:43  * jenkins-monitorquit (Remote host closed the connection)
17:29:56  * jenkins-monitorjoined
17:50:40  * jenkins-monitorquit (Remote host closed the connection)
17:50:50  * jenkins-monitorjoined
19:19:58  <mylesborins>jbergstroem are you around?
19:31:43  * jenkins-monitorquit (Remote host closed the connection)
19:31:55  * jenkins-monitorjoined
20:44:52  <jbergstroem>mylesborins: am
20:45:20  <mylesborins>all good
20:45:21  <mylesborins>:D
20:51:53  * Fishrock123joined
21:02:59  <jbergstroem>mylesborins: did you get my last two privmsgs?
21:03:28  <jbergstroem>mylesborins: (or are we - emphasis me - just incompetent enough to not set up otr properly)
21:04:33  * Fishrock123quit (Quit: Leaving...)
21:05:22  <mylesborins>yup
21:05:23  <mylesborins>I'm on a call and was talking so I missed it :D
21:05:37  <jbergstroem>call < lyf < irc