02:18:51  <Trott>Well, this is alarming on AIX:
02:18:55  <Trott>https://www.irccloud.com/pastebin/E5F3Pw2b/
02:19:06  <Trott>mhdawson_ ^^^^^^
02:19:11  <Trott>Guess I'll try to run again and see what happens....
02:19:28  <Trott>Oh, and that pastebin is from https://ci.nodejs.org/job/node-test-commit-aix/9578/nodes=aix61-ppc64/console
02:23:52  <refack>https://ci.nodejs.org/job/node-test-commit-aix/9579/nodes=aix61-ppc64/
02:24:01  <refack>Seems to get further
02:36:26  <Trott>refack: I don't think it did, actually. Looks to have failed in the exact same place, I think.
02:37:15  <Trott>Either way, another "fork() system call failed" failure. :-(
02:37:35  * refackgetting up to check things out
02:38:13  <Trott>Looks like it's running a bunch of citgm related jobs.
02:38:28  <Trott>Not sure if it's trying to run citgm and node-test-commit at the same time or if the citgm jobs are hung.
02:38:47  <Trott>AIX systems is not my strong suit. :-D
02:39:01  <refack>Hung citgm jobs are a thing on AIX
02:39:46  <Trott>So you or I should `kill -9` the hung jobs?
02:39:54  <Trott>(Or `pkill` if it exists on AIX?)
02:40:40  <Trott>Didn't need a `-9`, just a straight `kill <PID>`.
02:41:17  <refack>yeah, we haven't figured out why yet
02:41:47  <Trott>Maybe take AIX out of the citgm-smoker job? Just an idea.
02:42:13  <refack>Searching for the thread to comment that
02:42:56  <Trott>OK, I terminated all the citgm-smoker hung processes. Will restart that last node-test-commit-aix and see if it builds now.
02:43:06  <refack>https://github.com/nodejs/build/issues/900
02:47:40  * node-ghjoined
02:47:40  * node-ghpart
02:47:52  * node-ghjoined
02:47:52  * node-ghpart
02:51:16  <refack>Well job 9​58​0 is running on the other machine, so I started 9​58​1
03:07:25  <refack>Both jobs seems to have finished compiling
03:08:21  * joyeejoined
03:09:08  * refacknodding off to the soothing visual of logs rolling
05:54:17  * node-ghjoined
05:54:17  * node-ghpart
05:58:36  * node-ghjoined
05:58:36  * node-ghpart
06:32:08  * seishunjoined
07:32:27  * seishunquit (Ping timeout: 240 seconds)
07:39:59  * node-ghjoined
07:39:59  * node-ghpart
09:27:05  * node-ghjoined
09:27:05  * node-ghpart
09:40:22  * joyeequit (Remote host closed the connection)
09:50:30  * joyeejoined
09:55:34  * joyeequit (Ping timeout: 264 seconds)
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:40  * mylesborinsjoined
10:32:28  * joyeejoined
10:36:33  * joyeequit (Ping timeout: 246 seconds)
10:51:51  * node-ghjoined
10:51:51  * node-ghpart
11:03:51  * node-ghjoined
11:03:51  * node-ghpart
11:47:50  * joyeejoined
11:52:56  * node-ghjoined
11:52:56  * node-ghpart
12:13:09  * lance|afkchanged nick to lanceball
12:15:40  * lanceballquit (Changing host)
12:15:40  * lanceballjoined
13:03:37  * evanlucasjoined
13:32:01  * node-ghjoined
13:32:01  * node-ghpart
13:49:51  * maclover7joined
13:55:00  <maclover7>should the jenkins multijob plugin get updated?
13:55:05  <maclover7>there was a jenkins security release this morning
13:55:05  <maclover7>https://jenkins.io/security/advisory/2017-10-23/
13:56:28  <joyee>I think @jbergstroem mentioned we are not using that plugin?
13:58:58  <maclover7>...isn't node-test-commit a multijob job?
13:59:03  <maclover7>(I could be wrong)
14:31:12  <refack>Not sure if there's another plugin with a similar name, but yes we do use multijob
14:31:20  <refack>I'll ping gibson
14:58:10  * node-ghjoined
14:58:10  * node-ghpart
14:58:34  * node-ghjoined
14:58:34  * node-ghpart
15:35:13  * jasnelljoined
15:47:47  * node-ghjoined
15:47:52  * node-ghpart
15:47:54  * seishunjoined
15:49:57  * node-ghjoined
15:49:57  * node-ghpart
15:58:51  * node-ghjoined
15:58:51  * node-ghpart
15:59:45  * node-ghjoined
15:59:45  * node-ghpart
16:06:46  * node-ghjoined
16:06:46  * node-ghpart
16:16:53  * Fishrock123joined
16:18:12  * node-ghjoined
16:18:12  * node-ghpart
16:25:29  * joyeequit (Remote host closed the connection)
16:25:41  * node-ghjoined
16:25:41  * node-ghpart
16:26:06  * node-ghjoined
16:26:06  * node-ghpart
16:27:20  * node-ghjoined
16:27:20  * node-ghpart
16:27:50  * node-ghjoined
16:27:50  * node-ghpart
16:35:43  * joyeejoined
16:37:56  * node-ghjoined
16:37:56  * node-ghpart
16:40:33  * joyeequit (Ping timeout: 248 seconds)
16:41:35  * Fishrock123quit (Remote host closed the connection)
16:44:31  * evanlucasquit (Remote host closed the connection)
16:45:28  * gibfahnjoined
16:46:06  * Fishrock123joined
17:16:58  * Fishrock123quit (Remote host closed the connection)
17:17:15  * joyeejoined
17:18:10  * Fishrock123joined
17:19:03  * Fishrock123quit (Remote host closed the connection)
17:21:50  * joyeequit (Ping timeout: 258 seconds)
17:29:34  <ofrobots>Could someone with access to Jenkins take a look at my CI: https://ci.nodejs.org/job/node-test-pull-request/10865/ to see if looks green.
17:29:38  <ofrobots>I don't have access due to embargo
17:31:33  * seishunquit (Remote host closed the connection)
17:51:46  * Fishrock123joined
17:56:14  * Fishrock123quit (Ping timeout: 246 seconds)
18:18:28  * seishunjoined
18:30:10  * node-ghjoined
18:30:10  * node-ghpart
18:31:52  * Fishrock123joined
18:32:39  * node-ghjoined
18:32:39  * node-ghpart
18:33:21  * node-ghjoined
18:33:21  * node-ghpart
19:08:47  * joyeejoined
19:13:05  * joyeequit (Ping timeout: 248 seconds)
19:58:10  * node-ghjoined
19:58:10  * node-ghpart
20:21:21  * seishunquit (Ping timeout: 248 seconds)
20:23:18  <mylesborins>who still has access to CI right now who can debug some windows issues
20:25:39  <refack>I could probably help. I'm out of Jenkins but could help locally
20:25:43  * Fishrock123quit (Remote host closed the connection)
20:26:19  * Fishrock123joined
20:30:21  <mylesborins>its infra issue :p
20:30:26  <mylesborins>joaocgreis ^^^
20:30:49  * Fishrock123quit (Ping timeout: 258 seconds)
20:54:39  * node-ghjoined
20:54:39  * node-ghpart
21:07:24  * seishunjoined
21:13:14  * seishunquit (Ping timeout: 252 seconds)
21:15:16  * gibfahnquit (Quit: Connection closed for inactivity)
21:27:49  * Fishrock123joined
21:32:11  * Fishrock123quit (Ping timeout: 246 seconds)
21:46:30  * Fishrock123joined
21:58:17  * node-ghjoined
21:58:17  * node-ghpart
21:58:52  * node-ghjoined
21:58:52  * node-ghpart
22:26:42  * joyeejoined
22:33:05  * joyeequit (Ping timeout: 248 seconds)
22:36:29  <rvagg>mylesborins: windows issue?
22:36:51  <mylesborins>o/
22:36:53  <mylesborins>https://ci.nodejs.org/job/node-test-commit-windows-fanned/12769/
22:36:54  <mylesborins>having issues with citgm too
22:37:38  <rvagg>k, ssh creds inheritance thing I think, will try and fix
22:41:06  <mylesborins>danke shen
23:02:01  * joyeejoined
23:05:48  <rvagg>problem is that we're already using an ssh key to push to the private binaries repo for fanned builds yet we need to add another one to the environment to pull from github and it's different
23:06:16  <rvagg>can't figure out a way to select which key to use from ssh-agent when fetching so it just fails
23:06:28  <rvagg>... but ... perhaps we just add that binaries repo key to the node-private repo
23:06:35  * joyeequit (Ping timeout: 240 seconds)
23:14:49  <mylesborins>why is this different than any other env?
23:14:50  <mylesborins>and this is also a regression since the last time we ran these tests
23:17:26  <rvagg>mylesborins: I'm going to have to wait for joaocgreis to figure out why it's different now, maybe it's just a software upgrade thing, but these fanned builds are pretty complex so it's not surprising when little things break in surprising ways
23:18:49  <mylesborins>rvagg fair enough
23:18:54  <mylesborins>I guess I can use the non private jobs since CI is locked down
23:18:55  <mylesborins>¯\_(ツ)_/¯
23:28:25  <rvagg>mylesborins: working now, got a green on https://ci.nodejs.org/job/git-rebase/25129/, but it's required some hackery, I'll try and figure this out with joaocgreis and make something more permanent
23:28:59  <mylesborins>thanks. LMK when I'm good to rekick off jobs
23:29:02  <mylesborins>FWIW since I'm getting the same errors with the citgm job it might be a system thing from ansible rather than in a specific job
23:29:08  <mylesborins>unless that rebase job is shared
23:29:09  <rvagg>mylesborins: it should be ready now
23:29:20  <rvagg>start off with just one for now to confirm