00:00:15  <italoacasas>btw to test I'm using https://github.com/nodejs/abi-stable-node-addon-examples
00:00:55  <mylesborins>why are you using those ones?
00:01:05  <mylesborins>aren't those using experimental NAPI?
00:01:38  <mylesborins>best bet will just be doing an `npm install --build-from-source` of any native module
00:02:16  <italoacasas>sorry, I was looking at that ones to see the difference, https://github.com/nodejs/node-addon-examples
00:02:29  <mylesborins>ah ok
00:04:00  * sxaquit (Ping timeout: 268 seconds)
00:06:14  <mylesborins>npm install --build-from-source serialport
00:06:23  <mylesborins>that blows up on v7.7.0
00:08:36  * not-an-aardvarkjoined
00:09:42  <italoacasas>you're not going to be able to test that way using an rc
00:09:58  <italoacasas>this file is never going to exist https://nodejs.org/dist/v7.7.1-rc.1/node-v7.7.1-rc.1.tar.gz
00:10:06  <mylesborins>it isn't in dist
00:10:11  <mylesborins>it will work fine
00:10:11  * sxajoined
00:10:19  <mylesborins>NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/rc nvm install v7.7.1-rc.1
00:10:23  <mylesborins>unset NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/rc nvm install v7.7.1-rc.1
00:10:32  <mylesborins>npm install --build-from-source serialport
00:10:48  <mylesborins>that link... for where the headers are, is embedded i nthe release
00:10:57  <mylesborins>the only reason you are getting links trumped is because nvm sets that env var
00:12:01  <mylesborins>running right now
00:12:02  <mylesborins>will have results in a minute
00:12:03  <mylesborins>build worked
00:12:39  <mylesborins>I'm ok singing off on this release if CI + citgm are clean
00:12:43  <mylesborins>I can confirm headers are fine
00:13:20  <mylesborins>https://gist.github.com/MylesBorins/d983701a27608239ecc65c119ab66dc4/edit
00:44:35  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
00:57:09  * sxaquit (Ping timeout: 260 seconds)
01:00:35  * sxajoined
01:14:33  * chorrelljoined
01:20:19  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
02:23:45  * chorrelljoined
02:29:31  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
02:36:24  * jenkins-monitorquit (Remote host closed the connection)
02:36:34  * jenkins-monitorjoined
03:13:48  <Trott>test-osuosl-ubuntu14-ppc64_be-2 is consistently failing to build. Example: https://ci.nodejs.org/job/node-test-commit-plinux/nodes=ppcbe-ubuntu1404/7269/console https://ci.nodejs.org/job/node-test-commit-plinux/nodes=ppcbe-ubuntu1404/7272/console https://ci.nodejs.org/job/node-test-commit-plinux/nodes=ppcbe-ubuntu1404/7274/console
03:14:04  <Trott>Output looks like this:
03:14:21  <Trott>https://www.irccloud.com/pastebin/7q6X0mUY/
03:14:36  <Trott>mhdawson_ jbergstroem ^^^^
03:15:17  <jbergstroem>:
03:15:18  <jbergstroem>/
03:15:57  <jbergstroem>2sec
03:16:30  <jbergstroem>i swear michael closed an issue with the same error just a few hours ago
03:18:37  <jbergstroem>restarted
03:18:41  <jbergstroem>will update the client jar
03:20:01  <jbergstroem>[done]
05:11:34  <rvagg>jbergstroem: what are the -X flags passed to that java instance on the server? do you have it handy?
05:11:45  <rvagg>the PermGen error suggests we may need to bump something
07:07:37  * sxaquit (Ping timeout: 256 seconds)
07:10:44  * sxajoined
09:35:47  * node-ghjoined
09:35:47  * node-ghpart
09:35:55  * node-ghjoined
09:35:55  * node-ghpart
09:38:44  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
10:58:22  * sxaquit (Read error: Connection reset by peer)
10:58:45  * sxajoined
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
11:26:55  * node-ghjoined
11:26:55  * node-ghpart
11:28:25  * targosjoined
11:35:38  * node-ghjoined
11:35:38  * node-ghpart
12:31:31  <jbergstroem>rvagg: yeah bumped max ram to 192mb
13:12:51  * node-ghjoined
13:12:51  * node-ghpart
14:01:03  * chorrelljoined
15:45:27  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:54:09  * chorrelljoined
15:55:13  * jenkins-monitorquit (Remote host closed the connection)
15:55:21  * jenkins-monitorjoined
17:19:56  * node-ghjoined
17:19:56  * node-ghpart
17:20:28  * node-ghjoined
17:20:28  * node-ghpart
17:25:13  * node-ghjoined
17:25:13  * node-ghpart
17:29:06  * targosquit (Quit: Leaving)
17:29:32  * node-ghjoined
17:29:32  * node-ghpart
18:57:16  <Trott>test-osuosl-ubuntu14-ppc64_le-2 is failing consistently. Different error than be-2 above. But uh, maybe same thing? Example: https://ci.nodejs.org/job/node-test-commit-plinux/7297/nodes=ppcle-ubuntu1404/console
18:57:55  <Trott>https://www.irccloud.com/pastebin/G8kpkWGo/
18:59:28  <Trott>mhdawson_ jbergstroem ^^^^
19:35:16  <Trott>There's a zombie git process with Jenkins as the parent process. I'm going to restart jenkins to see if it gets rid of the zombie process and fixes the issue. Hopefully it does both.
19:36:06  <Trott>Well, that definitely got rid of the zombie git. Now to see if builds start working again....
19:40:37  <Trott>Won't know for sure until it times out after 20 minutes, but that doesn't look like it helped.
19:45:44  <Trott>Oh, well, guess I'll run updates on the off chance that fixes anything....
20:10:44  * jenkins-monitorquit (Remote host closed the connection)
20:10:55  * jenkins-monitorjoined
21:17:14  * jenkins-monitorquit (Remote host closed the connection)
21:17:25  * jenkins-monitorjoined
21:30:27  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
22:49:37  * evanlucasquit (Ping timeout: 240 seconds)
22:51:02  * evanlucasjoined
23:18:31  <Trott>Any ideas what to do to get the plinux machines working again? It looks like they've been failing for a few hours now. jbergstroem: mhdawson_ rmg_
23:19:05  <jbergstroem>Trott: In a cab. At a computer in ~1h but I'll raise ram and restart as soon as I can (if it helps)
23:19:17  <Trott>k thx, I'll be patient. :-D
23:22:32  <jbergstroem>Trott: don't you have access to it?
23:23:46  <Trott>I can log in. I tried restarting Jenkins and I updated packages for giggles, but neither changed the results.
23:23:58  <Trott>Oh, I also killed a zombie process. Also didn't help.
23:25:15  <Trott>Not sure how to give the server itself more memory. Or are you talking about just more memory assigned to the .jar process or something like that?
23:27:42  <jbergstroem>Trott: Yeah; the mx128mb flag
23:27:48  <Trott>Ah, OK.
23:28:23  <jbergstroem>get a new slave.jar too!
23:28:46  <jbergstroem> https://ci.nodejs.org/jnlpJars/slave.jar
23:29:22  <Trott>Download that and put it in place of the existing slave.jar on the server?
23:29:47  <Trott>I have a meeting right now, but will do this right after it's over unless someone beats me to it. Thanks!
23:29:47  <jbergstroem>yeah
23:29:58  <jbergstroem>Ok, see if I beat you to it
23:49:49  * not-an-aardvarkjoined