00:03:04  * rmgjoined
00:07:17  * rmgquit (Ping timeout: 244 seconds)
02:03:42  * rmgjoined
02:08:06  * rmgquit (Ping timeout: 246 seconds)
06:38:23  * node-ghjoined
06:38:23  * node-ghpart
07:59:36  * node-ghjoined
07:59:36  * node-ghpart
08:09:06  * rmgjoined
08:11:37  * node-ghjoined
08:11:38  * node-ghpart
08:13:55  * node-ghjoined
08:13:55  * node-ghpart
08:14:34  * rmgquit (Ping timeout: 272 seconds)
10:41:48  * thealphanerdquit (Quit: farewell for now)
10:42:19  * thealphanerdjoined
14:03:31  * Fishrock123joined
14:19:18  * node-ghjoined
14:19:18  * node-ghpart
14:55:10  * Eurcsijoined
14:55:11  * Eurcsipart
15:05:11  * jenkins-monitorquit (Remote host closed the connection)
15:05:12  * 16WAANNVQquit (Remote host closed the connection)
15:05:22  * jenkins-monitorjoined
15:05:32  * jenkins-monitor1joined
15:14:47  * rmgjoined
15:19:27  * node-ghjoined
15:19:27  * node-ghpart
15:19:33  * rmgquit (Ping timeout: 244 seconds)
16:47:01  * sgimenoquit (Quit: Leaving)
17:16:18  * rmg_joined
17:21:28  * rmg_quit (Ping timeout: 264 seconds)
17:44:30  <Trott>https://ci.nodejs.org/job/node-test-commit-plinux/2561/nodes=ppcbe-ubuntu1404/console looks like it's hung after 8+ hours....
17:45:55  <Trott>And smartos14-64 seems to have been having serious issues the last several days... https://ci.nodejs.org/job/node-test-commit-smartos/2594/nodes=smartos14-64/console. Tons of tests failing with `EADDRINUSE :::12346` but other operating systems aren't having the problem. At least, I'm *hoping* it's build-related and not a regression...
17:54:30  <Fishrock123>is the ppcbe build machine stuck?
17:54:43  <Fishrock123>e.g. https://ci.nodejs.org/job/node-test-pull-request/
17:54:50  <Fishrock123>lots of waiting jobs
17:57:32  <Trott>Fishrock123: It sure looks like it's stuck. https://ci.nodejs.org/job/node-test-commit-plinux/2561/nodes=ppcbe-ubuntu1404/console has been at the same line for a long time now....
18:00:11  <thealphanerd>just was looking at it myself
18:00:49  <thealphanerd>looks like they are all getting stuck at the same place
18:00:59  <thealphanerd>it's Victoria Day in Canada so I don't think michael___ will be around
18:01:13  <thealphanerd>although Fishrock123 is around so ¯\_(ツ)_/¯
18:05:29  * Fishrock123maybe shouldn't be around
18:05:41  <Fishrock123>I also completely forgot it was the long weekend
18:05:58  <Fishrock123>and I need things to keep me occupied before overwatch launches tonight
18:06:01  <Fishrock123><_<
18:07:08  <thealphanerd>heheh
18:07:17  <thealphanerd>so 2561 got halted during compilation
18:07:23  <thealphanerd>all the other boxes were waiting for it
18:08:03  <Trott>And jbergstroem is off traveling I think, so yeah, welcome to the horrible dystopian future we've all imagined: A CI INFRASTRUCTURE WORLD WITHOUT JOHAN!
18:08:08  <thealphanerd>I killed that one ppc job... the other job that was halted finished properly
18:08:16  <thealphanerd>the rest have now started to use those machines
18:08:29  <Fishrock123>hmmmmm https://ci.nodejs.org/job/node-test-commit-smartos/2602/nodes=smartos14-64/tapTestReport/
18:08:38  <Fishrock123>I *may* have broken something on smartos lol
18:08:44  <thealphanerd>so if 2563 or 2564 halt during compilation we may need to dig in further
18:08:48  <thealphanerd>Fishrock123 on master?
18:08:54  <Fishrock123>no
18:08:58  <Fishrock123>wait
18:09:01  <Fishrock123>are those all timeouts
18:09:06  <Fishrock123>I bet they are all timeouts
18:09:57  <thealphanerd>Fishrock123 there was a single timeout
18:10:05  <thealphanerd>oh
18:10:05  <thealphanerd>wait
18:10:13  <thealphanerd>nvm you are talking about smartos
18:10:17  <thealphanerd>feel free to ignore me :D
18:10:33  <Fishrock123>That's 78 EADDRINUSE
18:10:37  <Fishrock123>weird
18:12:10  <Trott>Yeah, the SmartOS issue has been going since...at least Saturday PDT>
18:12:31  <Trott>I *hope* it's a build/configuration issue and not an actual SmartOS-specific regression.
18:16:15  <Fishrock123>could just launch a run against v4.x to find out
18:27:56  <thealphanerd>I just ran a CI on v4.4.5-proposal
18:28:02  <thealphanerd>we can see if it fails there
19:03:27  <jbergstroem>did someone say beetlejuice
19:15:46  <jbergstroem>hm, everything seems to be working
19:16:07  * node-ghjoined
19:16:08  * node-ghpart
19:16:09  <jbergstroem>Trott: i thought thes martos thing was being worked on? (changed to common.port)
19:16:19  <jbergstroem>anyway gotta scram; be back soon ish
19:18:09  <jbergstroem>qlooks like we need some redundancy for ubuntu12
19:22:15  <thealphanerd>jbergstroem indeed!
19:22:19  <thealphanerd>Fishrock123 https://ci.nodejs.org/job/node-test-commit/3450/
19:22:24  <thealphanerd>smart os is looking fine on v4
19:22:38  <Fishrock123>try a run on master then i guess
19:22:56  <Fishrock123>probably can just start it from the smartos jobs
21:13:13  * Fishrock123quit (Remote host closed the connection)
22:18:51  * node-ghjoined
22:18:51  * node-ghpart
22:20:09  * rmgjoined
22:24:53  * rmgquit (Ping timeout: 250 seconds)
22:53:40  * othiym23quit (*.net *.split)
22:53:42  * rvaggquit (*.net *.split)
22:53:42  * michael___quit (*.net *.split)
22:53:45  * bretquit (*.net *.split)
23:20:53  * rmgjoined
23:25:03  * rmgquit (Ping timeout: 240 seconds)
23:38:55  * rvaggjoined