00:30:50  * Fishrock123joined
00:36:12  * Fishrock123quit (Ping timeout: 246 seconds)
00:40:02  * Fishrock123joined
00:51:13  * node-ghjoined
00:51:13  * node-ghpart
02:39:31  * apapirovskijoined
02:45:23  * Fishrock123quit (Remote host closed the connection)
03:09:33  * apapirovskiquit (Read error: Connection reset by peer)
03:10:11  * Fishrock123joined
03:20:08  * Fishrock123quit (Quit: Leaving...)
04:13:08  * node-ghjoined
04:13:08  * node-ghpart
05:00:20  <rvagg>refack: you broke the pi builds with https://ci.nodejs.org/job/node-test-binary-arm/jobConfigHistory/showDiffFiles?timestamp1=2017-11-05_03-13-42&timestamp2=2017-11-13_20-05-37
05:01:04  <rvagg>refack: they're all failing now with bad arguments to `kill`, e.g. https://ci.nodejs.org/job/node-test-binary-arm/11769/RUN_SUBSET=addons,label=pi2-raspbian-wheezy/console
05:06:54  <rvagg>refack: changed to `ps -ef | grep "\[node\] <defunct>" | awk '{print $2}' | xargs -rl kill || true`
05:07:39  <rvagg>-r to make xargs not run if there are no args (which is why these are failing), -l to run one `kill` per process, `|| true` to not fail the script if it can't perform the kill for whatever reason, i.e. don't make it fatal
07:35:29  * seishunjoined
08:36:43  * node-ghjoined
08:36:43  * node-ghpart
08:44:16  * seishunquit (Ping timeout: 248 seconds)
09:57:22  * node-ghjoined
09:57:22  * node-ghpart
11:25:12  * mylesborinsquit (Quit: farewell for now)
11:25:42  * mylesborinsjoined
11:45:35  <refack>Yeah. I should not have done it last thing of the day... I tested one build.
11:46:52  <refack>Also now that I think of it. I put that line in a non effective place (it's after the git clean, and before the make test-ci)
11:52:30  * node-ghjoined
11:52:30  * node-ghpart
12:09:59  * node-ghjoined
12:10:00  * node-ghpart
13:59:18  * evanlucasjoined
14:26:03  * qbitquit (Quit: WeeChat 1.9.1)
15:03:49  * qbitjoined
16:57:03  * Fishrock123joined
17:19:34  * Fishrock123quit (Remote host closed the connection)
17:28:32  * seishunjoined
17:35:32  * seishunquit (Ping timeout: 260 seconds)
17:39:05  * Fishrock123joined
18:47:01  * seishunjoined
18:48:54  <seishun>refack: to clarify, I would be happy to work on upgrading the other machines, but the comment I linked makes me doubt that all machines are going to be upgraded
18:50:26  <refack>Sure. I admit it's a bit of a mess...
18:56:54  * apapirovskijoined
19:16:06  * apapirovskiquit (Remote host closed the connection)
19:24:08  * apapirovskijoined
19:35:49  * Fishrock123quit (Remote host closed the connection)
19:37:25  * Fishrock123joined
19:41:53  * Fishrock123quit (Ping timeout: 250 seconds)
19:51:25  * apapirovskiquit (Remote host closed the connection)
19:51:29  * Fishrock123joined
19:54:29  * apapirovskijoined
19:59:02  * apapirovskiquit (Ping timeout: 260 seconds)
20:04:27  * node-ghjoined
20:04:27  * node-ghpart
20:31:54  * Fishrock123quit (Remote host closed the connection)
20:37:50  * Fishrock123joined
21:00:53  * node-ghjoined
21:00:53  * node-ghpart
21:02:42  * gibfahn_joined
21:02:43  * node-ghjoined
21:02:43  * node-ghpart
21:06:21  * node-ghjoined
21:06:22  * node-ghpart
21:06:58  * node-ghjoined
21:06:58  * node-ghpart
21:28:07  * seishunquit (Remote host closed the connection)
21:30:05  <Trott>test-digitalocean-alpine35_container-x64-1 seems to be perma-fail right now: https://ci.nodejs.org/computer/test-digitalocean-alpine35_container-x64-1/builds (5 in a row, most recent success was 6 hours ago)
21:30:34  <Trott>test-digitalocean-alpine35_container-x64-2 seems to be building just fine.
21:31:11  <Trott>I'm going to take test-digitalocean-alpine35_container-x64-1 offline. Not sure who to ping on that one, so I'm going to ping broadly. Sorry for the noise. jbergstroem rvagg refack gibfahn_ joaocgreis
21:31:44  <refack>it's rvagg but I'm looking at the logs and they are weird
21:34:59  <refack>looks like two build jobs interleaved
21:35:04  <refack>https://www.irccloud.com/pastebin/FWBUXcqM/
21:35:58  * Fishrock123quit (Remote host closed the connection)
21:44:27  <rvagg>refack: the interleaving is probably just because of `-j 4`. `env: can't execute './node': Permission denied` seems to be the interesting bit
21:45:09  <refack>node-gyp is trying to use the executable while it's being linked
21:45:28  <refack>`make` is messing up the dependencies
21:46:44  <rvagg>I'm not quite sure that's it though
21:46:52  <rvagg>log in to test-digitalocean-ubuntu1604-docker-x64-1
21:47:03  <rvagg>go to /home/iojs/test-digitalocean-alpine35_container-x64-1/build/workspace/node-test-commit-linux/nodes/alpine35-container-x64
21:47:14  <rvagg>then try to run `./node` or `./out/Release/node`
21:47:26  <rvagg>the file is there, but `bash: ./out/Release/node: No such file or directory`
21:47:40  <rvagg>I guess it _could_ be that it's not fully linked yet
21:48:50  <refack>It seems like there a successful node-gyp call up the log (assuming it's using a previously linked node binary)
21:49:14  <rvagg>mm, yeah
21:49:37  <rvagg>hm, this in syslog: `[483387.960932] traps: node[21272] trap invalid opcode ip:56442cc548f9 sp:7ffd15e29ed8 error:0 in node[56442ba30000+1c96000]`
21:49:39  <refack>first guess clock issue
21:50:51  <rvagg>hah, google brings up https://github.com/nodejs/node/issues/15798 as first result for "trap invalid opcode"
21:50:53  <rvagg>I think it's a legit bug
21:51:54  <rvagg>why it's working for a while then won't even start though
21:51:56  <rvagg>oh actually
21:52:12  <rvagg>duh, I need to be running it in the alpine container, can't run the alpine executable on ubuntu
21:54:36  <rvagg>yeah, executable works fine inside the container
21:58:23  <rvagg>hm, I can do `run-ci` inside the container just fine, builds the addons and all
21:58:32  * {slurp-nodejs}1joined
21:58:32  * jbergstroemtopic: we're the nodejs build group. https://ci.nodejs.org https://github.com/nodejs/build -- irc logs: http://logs.libuv.org/node-build/latest
21:59:38  <rvagg>hm, I can do `run-ci` inside the container just fine, builds the addons and all
21:59:39  * {slurp-nodejs}quit (Ping timeout: 250 seconds)
22:00:48  <rvagg>stopping and deleting the image and its work directory, running ansible again to create and start it and we'll see if this makes a difference
22:01:11  <refack>K
22:04:33  <refack>Could you merge https://github.com/nodejs/build/pull/992
22:12:35  <rvagg>yeah, I have a couple of tweaks staged first
22:13:34  * node-ghjoined
22:13:35  * node-ghpart
22:13:44  * node-ghjoined
22:13:45  * node-ghpart
22:14:01  * node-ghjoined
22:14:01  * node-ghpart
22:15:21  * node-ghjoined
22:15:22  * node-ghpart
22:18:19  * Fishrock123joined
22:37:56  * node-ghjoined
22:37:56  * node-ghpart
22:40:36  * node-ghjoined
22:40:36  * node-ghpart
23:02:51  * lanceballchanged nick to lance|afk
23:07:03  <Trott>test-digitalocean-fedora24-x64-1 has failed to build twice in a row. Something's probably up and worth looking at there...
23:07:35  <Trott>Most recent failure: https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora24/14120/console
23:08:21  <refack>Same thing as in the Dockers
23:08:34  <refack>I'll check for changes in Makefile
23:08:39  <Trott>👍
23:20:46  * Fishrock123quit (Remote host closed the connection)
23:23:21  <rvagg>new alpine container is back up and working (green) https://ci.nodejs.org/job/node-test-commit-linux/nodes=alpine35-container-x64/14121/
23:34:16  * node-ghjoined
23:34:16  * node-ghpart
23:45:30  * evanlucasquit (Remote host closed the connection)