00:15:38  <Trott>Now I'm having the same problem with https://ci.nodejs.org/job/node-stress-single-test-pi1-binary/ that I was having with https://ci.nodejs.org/job/node-stress-single-test/: Can't start jobs at all.
00:16:14  <Trott>Oh, wait, I got a job started in node-stress-single-test just now. Hooray me, and everyone else, and whoever fixed it?
00:16:41  <Trott>Of course, those jobs are failing *instantly* with null pointer exceptions.... :-|
00:17:35  <Trott>https://www.irccloud.com/pastebin/8K3USw3I/
00:18:03  <Trott>Switching to Pi 2 instead of Pi 1 fixed the instant failure issue.
01:31:14  * chorrelljoined
01:47:03  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
01:55:18  * williamkapkequit (*.net *.split)
01:55:59  * williamkapkejoined
03:04:25  <joyee>Quick question: what's the gcc version in our ARM hosts?
03:04:27  <joyee>https://github.com/nodejs/node/pull/14901#issuecomment-358481545
03:04:49  <joyee>The node-test-commit-arm ones, not the pis
03:30:06  * orangemochaquit (*.net *.split)
03:30:07  * addaleaxquit (*.net *.split)
03:30:07  * othiym23quit (*.net *.split)
03:30:07  * joaocgreisquit (*.net *.split)
03:31:05  * orangemochajoined
03:31:13  * othiym23joined
03:31:22  * joaocgreisjoined
03:31:25  * addaleaxjoined
03:57:19  * apapirovskijoined
03:58:54  * apapirovskiquit (Remote host closed the connection)
04:00:12  * apapirovskijoined
04:11:36  * apapirovskiquit (Remote host closed the connection)
04:26:51  * apapirovskijoined
04:27:05  * apapirovskiquit (Client Quit)
10:43:40  * seishunjoined
11:25:28  * mylesborinsquit (Quit: farewell for now)
11:25:59  * mylesborinsjoined
11:47:19  * node-ghjoined
11:47:19  * node-ghpart
12:10:29  * node-ghjoined
12:10:29  * node-ghpart
12:15:08  <rvagg>jenkins restarted (plugins updated too), a few workers have been cleaned up, upgraded and rebooted, we'll see how a new day treats it
13:19:33  * node-ghjoined
13:19:34  * node-ghpart
14:16:52  * node-ghjoined
14:16:52  * node-ghpart
14:34:33  <Trott>joyee: gcc on test-mininodes-ubuntu1604-arm64_odroid_c2-3:
14:34:35  <Trott>https://www.irccloud.com/pastebin/yEjguHFX/
14:35:22  <Trott>Not sure about the other hosts, but that was the one that I'm able to log into. :-D
14:35:30  <joyee>Trott: thanks
14:41:04  * evanlucasjoined
16:18:18  * qbitquit (Quit: WeeChat 2.0)
16:24:29  * qbitjoined
17:59:24  <joyee>anyone knows how to trigger sequential tests properly in the stress test job?
17:59:45  <joyee>bumping into a lot of EACCES on common.PIPE
20:20:15  * node-ghjoined
20:20:15  * node-ghpart
20:24:50  * node-ghjoined
20:24:50  * node-ghpart
20:57:03  * seishunquit (Ping timeout: 268 seconds)
21:32:11  <Trott>joyee: I've never seen that. Can you send a link? (Or did you figure it out?)
21:33:39  <joyee>https://ci.nodejs.org/job/node-stress-single-test/1713/
21:34:48  <joyee>And on master https://ci.nodejs.org/job/node-stress-single-test/1712
21:35:52  <joyee>Uh, wait, I think it's an actual EACCES issue because that looks like something under /tmp and it failed 100%
21:43:33  <joyee>It's probably because test-digitalocean-alpine34_container-x64-1 have not configured the permission properly..
21:43:47  <joyee>because test-softlayer-ubuntu1604-x64-1 works fine
21:44:28  <joyee>s/test-softlayer-ubuntu1604-x64-1/test-softlayer-alpine36_container-x64-1
21:51:38  * seishunjoined
22:00:32  * evanlucasquit (Remote host closed the connection)
23:07:36  * apapirovskijoined
23:44:15  * apapirovskiquit (Remote host closed the connection)
23:47:48  * apapirovskijoined
23:53:13  * seishunquit (Ping timeout: 256 seconds)
23:54:22  * apapirovskiquit (Remote host closed the connection)