00:21:29  <mylesborins>thanks rvagg
00:21:41  <rvagg>finished and in staging, nice and quick
00:21:44  <rvagg>mylesborins: ^
00:22:13  <mylesborins>🎉
00:27:27  <mylesborins>rvagg https://github.com/nodejs/node/pull/16848#issuecomment-342334153
00:27:37  <mylesborins>looks like the clang / gcc on our arm cluster is too old
00:27:38  <mylesborins>:(
00:27:57  <mylesborins>https://ci.nodejs.org/job/node-test-commit-arm-fanned/12341/
00:29:17  <mylesborins>https://github.com/nodejs/build/issues/982
00:29:20  * node-ghjoined
00:29:20  * node-ghpart
00:29:33  <refack>I think it's another artifact of the V8 bump
00:29:44  <refack>I've seen a patch for that upstream
00:41:56  * Fishrock123joined
00:42:04  <rvagg>thanks for sorting out nightlies joaocgreis
00:46:57  * Fishrock123quit (Ping timeout: 240 seconds)
01:05:44  * gibfahn_quit (Quit: Connection closed for inactivity)
01:05:44  * gibfahnquit (Quit: Connection closed for inactivity)
01:34:53  * Fishrock123joined
01:44:11  <joaocgreis>rvagg: 👍
01:56:47  <Trott>Anybody know what's up with AIX? IIt was slow earlier, but now it seems to be toast.
02:00:06  * rvaggclaims ignorance
02:02:13  <Trott>Actually, lots of CI weirdness right now. Will have to look for a pattern/consistency....
02:05:51  <Trott>If I'm logged into Jenkins and go to a pull-request result page like https://ci.nodejs.org/job/node-test-pull-request/11241/ and click Rebuild, I get a form. All well and good. If I submit that form, nothing happens. No build is kicked off or anything.
02:08:19  <maclover7>build queue should be pretty short right now, right?
02:10:45  <Trott>I'm able to start jobs the usual way. Build queue seems short to me but I may not know where to look to see *everything*....
02:11:29  <Trott>There's definitely something weird up. LIke this: https://ci.nodejs.org/job/node-test-commit-freebsd/13025/
02:11:40  <Trott>Job "failed" but nothing ran...
02:12:41  <Trott>Might be OK now. Restarting a bunch of these weird failures manually and not seeing anything alarming (yet)
02:18:38  <Trott>Aside: Rebuild functionality seems broken entirely as far as I can tell.
02:18:52  <Trott>(As in the "Rebuild" button that was so awesome and added relatively recently.)
02:26:10  <rvagg>Trott: this weirdness happens when you have all machines offline for one of the labels, aix in this case I guess
02:26:22  <rvagg>will have a look
02:26:41  <Trott>Weirdness may have passed.
02:27:00  <Trott>I re-ran six or so of the jobs that had the weird results and so far no more weirdness.. rvagg
02:27:49  <rvagg>I still scratch my head wondering why AIX is still a thing these days
02:31:38  <maclover7>looks like there's only one (usually two) aix machine working
02:31:42  <maclover7>the other was disabled
02:37:16  <rvagg>I'm on there doing a cleanup to see if that'll help
03:14:46  <refack>AIX 2 had a bee in it bonnet, so I tried to clear the workspace but it took forever to finish and I had to go AFK.
03:15:10  <refack>They are not a bottle neck usually
03:34:14  * Fishrock123quit (Quit: Leaving...)
07:37:47  * sgimenojoined
07:42:47  * seishunjoined
08:01:16  * joyeequit (Ping timeout: 255 seconds)
08:01:38  * joyeejoined
08:04:50  * sgimeno_joined
08:05:57  * sgimenoquit (Ping timeout: 240 seconds)
08:25:35  * seishunquit (Ping timeout: 240 seconds)
08:27:27  * xadillaxjoined
08:31:07  * sgimeno__joined
08:33:02  * sgimeno_quit (Ping timeout: 260 seconds)
08:40:37  * sgimeno__quit (Ping timeout: 260 seconds)
08:43:35  * xadillaxquit (Ping timeout: 240 seconds)
08:44:46  * sgimeno__joined
08:51:03  * sgimeno_joined
08:54:09  * sgimeno__quit (Ping timeout: 268 seconds)
09:09:52  * xadillaxjoined
09:14:30  * xadillaxquit (Ping timeout: 268 seconds)
09:19:25  * sgimeno_quit (Ping timeout: 250 seconds)
09:19:31  * node-ghjoined
09:19:31  * node-ghpart
09:21:43  * sgimeno_joined
09:52:20  * xadillaxjoined
10:02:18  * xadillaxquit (Remote host closed the connection)
10:11:39  * xadillaxjoined
10:13:34  * sgimeno__joined
10:14:06  * sgimeno_quit (Ping timeout: 258 seconds)
10:15:05  <Trott>"Rebuild" button seems to be working again. 🎉
10:25:52  * xadillaxquit (Remote host closed the connection)
10:28:19  * sgimeno__quit (Ping timeout: 250 seconds)
10:28:42  * sgimeno__joined
10:30:52  <Trott>refack: Any chance of getting that second AIX machine back online? Should I just try enabling it again and seeing what happens, then disable it again if it is acting up?
10:32:59  * node-ghjoined
10:32:59  * node-ghpart
10:33:31  * sgimeno__quit (Ping timeout: 250 seconds)
10:36:47  * sgimeno__joined
10:40:13  * sgimeno_joined
10:43:03  * sgimeno__quit (Ping timeout: 250 seconds)
10:52:45  <rvagg>Trott: I've cleaned and rebooted it, brought it back online now and will see how it goes chomping at this queue
10:56:15  * xadillaxjoined
11:00:52  * xadillaxquit (Ping timeout: 258 seconds)
11:14:59  * xadillaxjoined
11:20:11  * xadillaxquit (Remote host closed the connection)
11:20:19  * xadillaxjoined
11:25:12  * mylesborinsquit (Quit: farewell for now)
11:25:43  * mylesborinsjoined
11:27:15  * sgimeno_quit (Ping timeout: 250 seconds)
11:28:25  * sgimeno_joined
11:32:14  <rvagg>one test failure, no git or jenkins errors at least https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix61-ppc64/10064/
11:42:22  <rvagg>dat queue
11:48:33  <Trott>For the more straightforward PRs, I'm tempted to cancel AIX and treat as success. Shortage of AIX resources is single-handedly delaying multiple CI jobs by many hours.
12:11:01  <rvagg>hm, yeah that's not o good
12:11:17  <rvagg>aix repeated failures on parallel/test-repl-envvars
12:19:17  <Trott>rvagg: Is it tied to a single AIX host? Maybe the one that was offline?
12:20:06  <rvagg>Trott: was only looking at test-osuosl-aix61-ppc64_be-2, the one that was offline, that test failed on both of the runs that were done after it was brought back
12:40:26  * xadillaxquit (Remote host closed the connection)
12:40:53  * xadillaxjoined
12:45:22  * xadillaxquit (Ping timeout: 264 seconds)
13:36:35  * sgimeno_quit (Ping timeout: 268 seconds)
13:49:07  * sgimeno_joined
13:54:23  * evanlucasjoined
14:35:47  * lance|afkchanged nick to lanceball
16:36:08  <joyee>Hi, am I correct in guessing that the arm machines do not support ipv6?
16:36:38  <joyee>The raspberry pis
16:41:55  <Trott>I took test-osuosl-aix61-ppc64_be-2 offline because it running node-test-commit-aix was a sea of red with failures on parallel/test-repl-envvars. I *think* this is a build thing and not a test issue. Anyone have any better information on that, though? mhdawson_
16:42:03  <refack>Oh it
16:42:14  <refack>on
16:46:25  * node-ghjoined
16:46:26  * node-ghpart
16:46:53  * Fishrock123joined
16:56:17  * seishunjoined
17:02:57  * Fishrock123quit (Remote host closed the connection)
17:03:33  * Fishrock123joined
17:07:51  * Fishrock123quit (Ping timeout: 250 seconds)
17:23:43  * Fishrock123joined
17:30:07  * Fishrock123quit (Remote host closed the connection)
17:37:34  * sgimeno_quit (Ping timeout: 264 seconds)
17:45:43  * Fishrock123joined
17:50:20  * sgimeno_joined
17:59:27  * Fishrock123quit (Quit: Leaving...)
18:00:59  * Fishrock123joined
19:16:36  * Fishrock123quit (Remote host closed the connection)
19:17:12  * Fishrock123joined
19:21:19  * Fishrock123quit (Ping timeout: 250 seconds)
19:25:37  * Fishrock123joined
20:04:58  * gibfahn_joined
20:06:43  <cxreg>gibfahn_: having fun with http2?
20:06:53  <gibfahn_>Yeah of course!
20:07:05  <cxreg>I'm watching CI with great amusement
20:07:06  <gibfahn_>Nothing better than test failures when you're trying to ship a build 😁
20:09:51  <cxreg>I haven't seen anything fail except that one http2 flaky test with rstWithProtocolError, is there more?
20:12:04  <cxreg>well that and https://github.com/nodejs/build/issues/984 I guess
20:12:34  <gibfahn_>https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1066/
20:12:53  <gibfahn_>The real fun is triaging CitGM
20:30:55  <maclover7>phillipj: are you able to check the github-bot logs real quick?
20:31:12  <maclover7>tried sending a few http-parser status requests, but doesn't seem to be doing anything
20:38:10  <phillipj>Sure! I can even send you the curl / bunyan command I use
20:38:34  <maclover7>even better! :)
20:48:02  * seishunquit (Ping timeout: 260 seconds)
21:10:14  * seishunjoined
21:15:43  * seishunquit (Ping timeout: 248 seconds)
21:47:56  * Fishrock123quit (Remote host closed the connection)
21:48:34  * node-ghjoined
21:48:34  * node-ghpart
21:58:07  * Fishrock123joined
22:55:33  * node-ghjoined
22:55:34  * node-ghpart
23:03:09  * evanlucasquit (Remote host closed the connection)
23:06:43  * node-ghjoined
23:06:43  * node-ghpart
23:12:01  * node-ghjoined
23:12:02  * node-ghpart
23:12:24  * Fishrock123quit (Remote host closed the connection)
23:53:32  * Fishrock123joined
23:57:57  * Fishrock123quit (Ping timeout: 246 seconds)