01:39:38  * node-ghjoined
01:39:38  * node-ghpart
02:01:44  * BridgeAR1quit (Ping timeout: 260 seconds)
03:28:56  * node-ghjoined
03:28:56  * node-ghpart
03:37:01  * node-ghjoined
03:37:01  * node-ghpart
03:53:17  * node-ghjoined
03:53:17  * node-ghpart
08:42:41  * BridgeAR1joined
08:57:47  * seishunjoined
10:25:10  * mylesborinsquit (Quit: farewell for now)
10:25:20  * mylesborinsjoined
10:45:53  * seishunquit (Ping timeout: 248 seconds)
12:07:50  * BridgeAR1quit (Ping timeout: 256 seconds)
12:08:34  * BridgeAR1joined
12:14:15  * seishunjoined
13:09:47  * node-ghjoined
13:09:48  * node-ghpart
13:16:29  * node-ghjoined
13:16:29  * node-ghpart
13:26:51  * node-ghjoined
13:26:51  * node-ghpart
13:34:04  * node-ghjoined
13:34:04  * node-ghpart
13:41:46  * node-ghjoined
13:41:46  * node-ghpart
14:39:09  * sxajoined
16:53:38  * node-ghjoined
16:53:38  * node-ghpart
16:54:14  <Trott>test-macstadium-macos10.12-x64-1 seems to fail a lot but I'm not sure why. https://ci.nodejs.org/computer/test-macstadium-macos10.12-x64-1/builds
16:56:10  <Trott>Most recently, it looks like this:
16:56:13  <Trott>https://www.irccloud.com/pastebin/662b7c68/
16:57:03  <rvagg>hm, could be a resource availability thing, those macstadium machines are fairly minimal
16:58:08  <Trott>Oh, that makes sense. Here's the failure before that one. Different but sure looks to be about resources:
16:58:11  <Trott>https://www.irccloud.com/pastebin/RWZ9IRNM/
16:58:37  <Trott>Oh, wait, that may not be (directly) about resources. I misunderstood "no available node".
16:59:39  <Trott>So what do we do? Is the thing to do to try to reduce `--jobs` from `2` to `1`? I'm pretty ignorant about how all this works.
17:07:54  <rvagg>Trott: could try, that may be a sync thing, not sure about that specific one though, it looks a bit different to other make problems
17:10:16  <Trott>Didn't do a thorough check but it looks like test-macstadium-macos10.12-x64-2 is having similar issues. Usually succeeds but fails a lot.
17:10:35  <Trott>Also: Hey everyone! Congratulations on a full week of green node-daily-master jobs! That hasn't happened in a while! https://ci.nodejs.org/job/node-daily-master/
17:29:50  * sxaquit (Ping timeout: 256 seconds)
17:31:53  <Trott>Ugh, when you scratch at a problem.... seeing it on test-macstadium-macos10.11-x64-1 too. So, basically, everywhere.
17:33:59  <Trott>That spawn one is showing up more than once:
17:34:01  <refack>I've seen `Error: spawn /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1012/out/Release/node ENOENT` a few days ago. Was hoping it was a flake
17:34:02  <Trott>https://www.irccloud.com/pastebin/UgUCGVTt/
17:34:31  <Trott>Looks to be pretty frequent. OS X is suddenly our least reliable platform in CI. :-|
17:35:39  <refack>We did add a bunch of macOS versions and relay more on MacStadium, so it's not too surprising
17:36:07  <refack>We might have a problem with FS races for the node binary, that we never detected before
17:37:14  <refack>Since building an addon requires actually reading the binary file (for exported symbols) _while_ executing it
17:41:10  <refack>And building the addons in parallel is just a month and a half old https://github.com/nodejs/node/commit/cea10baa221e7ed3c5408d526dcec4fb7a6e99fa
18:18:57  * seishunquit (Ping timeout: 240 seconds)
18:38:18  * seishunjoined
20:56:09  * seishunquit (Ping timeout: 264 seconds)
21:20:10  * seishunjoined
21:47:21  * seishunquit (Ping timeout: 244 seconds)
21:57:10  <Trott>Relevant perhaps: https://github.com/nodejs/node/pull/21978#issuecomment-408546077
21:57:22  <Trott>"it looks like it starts building addons before out/Release/node is created … that shouldn’t happen, as I understand the Makefile"
21:59:53  <refack>Can't be so since node-gyp is only called by `tools/build-addons.js` which can only be run by node
22:00:10  <refack>I'll open a tracking issue
22:06:51  * mkaczorjoined
22:08:39  * mkaczor1joined
22:19:10  * mkaczor1quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
22:28:42  * mkaczorpart
22:36:23  <refack>https://github.com/nodejs/node/issues/22006
23:42:56  <refack>Since this is first time I've seen this (https://ci.nodejs.org/job/node-test-commit-osx/nodes=osx1011/19994/ canary build), my current working assumption is that this is due to some new dependency cycle introduced by V8 6.4
23:59:35  * sxajoined