00:27:27  * jgijoined
00:39:47  * rmgjoined
00:44:22  * rmgquit (Ping timeout: 250 seconds)
00:55:42  * jgiquit (Quit: jgi)
00:56:56  * jgijoined
01:21:49  * jgiquit (Quit: jgi)
02:18:44  * jgijoined
02:19:12  * evanluca_changed nick to evanlucas
02:40:32  * rmgjoined
02:40:45  * jgiquit (Quit: jgi)
02:43:05  * jgijoined
02:43:45  * jgiquit (Client Quit)
02:45:08  * rmgquit (Ping timeout: 246 seconds)
03:04:07  * jgijoined
03:15:50  * jgiquit (Quit: jgi)
03:33:51  * jgijoined
03:35:08  * jgiquit (Client Quit)
03:54:07  * jgijoined
03:55:52  * jgiquit (Client Quit)
04:00:33  <jbergstroem>(jenkins was dead)
04:41:32  * rmgjoined
04:46:03  * rmgquit (Ping timeout: 260 seconds)
05:03:56  * jgijoined
05:18:56  * jgiquit (Quit: jgi)
05:19:23  <jbergstroem>wtf, the resume build is enabled again
05:22:03  * jgijoined
05:24:56  <jbergstroem>fyi, i did some testing this morning for 1.644 and just upgraded in production; all looks good. no plugins updated since its harder to test (and track all changes)
06:05:29  * jgiquit (Quit: jgi)
06:05:52  * jgijoined
06:06:02  * jgiquit (Client Quit)
06:12:57  * trottjoined
06:14:17  <trott>I keep trying to do stress tests for freebsd102-64 against my own repo, and it keeps coming back green after about 2 seconds. No tests are run. Maybe I'm just doing something wrong?
06:14:35  <jbergstroem>ill have a look
06:14:38  <jbergstroem>got a test url?
06:14:40  <trott>Example: https://ci.nodejs.org/job/node-stress-single-test/330/
06:15:18  <trott>Same thing for everyone from 326 up to 330. Won't be surprised in the least if it's me typo'ing somewhere, but I'm not seeing it....
06:23:21  <jbergstroem>it doesn't seem to be matching
06:26:00  <trott>It's strange because I was ran two or three on freebsd102-64 before I started having the problem consistently.
06:26:18  <trott>For giggles, let me try again...
06:27:30  <trott>And now it's working fine. (331) ¯\_(ツ)_/¯
06:30:16  <trott>While we're at it, any idea why https://ci.nodejs.org/job/node-test-commit-arm/1695/ seems to be holding up all the subsequent arm jobs?
06:31:00  <trott>Like if you look at https://ci.nodejs.org/job/node-test-commit-arm/1696/, it seems to be waiting on 1695 to finish armv7-ubuntu1404 even though that job is actually done.
06:37:33  <trott>(And now FreeBSD is back to it again: https://ci.nodejs.org/job/node-stress-single-test/332/nodes=freebsd102-64/)
07:07:19  * trottquit (Quit: leaving)
07:10:48  <jbergstroem>can't see any differences between the bots
07:11:03  <jbergstroem>but it seems like the first one isn't executing while the second is
07:11:10  <jbergstroem>i'll have a closer look after dinner
07:48:16  * evanlucasquit (Quit: Textual IRC Client: www.textualapp.com)
09:51:43  <jbergstroem>got the armv7 back online
10:01:32  * jbergstroem_joined
10:02:20  * jbergstroemquit (Excess Flood)
10:02:45  * jbergstroem_changed nick to jbergstroem
10:10:00  * bnoordhuisjoined
10:13:10  * imjacobclarkjoined
11:02:50  * bnoordhuisquit (Ping timeout: 272 seconds)
11:47:27  * imjacobc_joined
11:47:47  * imjacobclarkquit (Remote host closed the connection)
12:09:10  * bnoordhuisjoined
12:14:07  * bnoordhuisquit (Ping timeout: 265 seconds)
13:54:43  * imjacobc_quit (Remote host closed the connection)
13:55:43  * imjacobclarkjoined
13:57:56  * imjacobc_joined
13:59:36  * imjacob__joined
13:59:36  * imjacobc_quit (Remote host closed the connection)
13:59:41  * imjacob__quit (Remote host closed the connection)
14:00:09  * imjacobclarkquit (Remote host closed the connection)
14:00:11  * imjacobc_joined
14:02:25  * imjacobc_quit (Remote host closed the connection)
14:02:32  * imjacobclarkjoined
14:18:38  * chorrelljoined
15:36:07  * imjacobclarkquit (Ping timeout: 260 seconds)
15:40:49  * imjacobclarkjoined
15:48:26  * bnoordhuisjoined
16:27:17  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:31:39  * chorrelljoined
16:53:31  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:54:20  * bnoordhuisquit (Ping timeout: 272 seconds)
17:04:24  * rmgjoined
17:06:37  * Fishrock123joined
17:06:59  <joaocgreis>jbergstroem: re freebsd not running, looks like test-digitalocean-freebsd10-x64-1 does not have OSTYPE defined
17:07:41  * jgijoined
17:18:38  * rmgquit (Read error: Connection reset by peer)
17:20:04  * rmgjoined
17:51:55  * jgiquit (Quit: jgi)
17:55:31  * imjacobclarkquit (Remote host closed the connection)
17:58:14  * jgijoined
17:58:52  * jgiquit (Client Quit)
18:00:16  * bnoordhuisjoined
18:00:34  * jgijoined
18:01:03  * jgiquit (Client Quit)
18:04:44  * bnoordhuisquit (Ping timeout: 256 seconds)
18:30:07  * jgijoined
18:30:31  * bnoordhuisjoined
18:50:50  * chorrelljoined
19:10:28  * bnoordhuisquit (Ping timeout: 256 seconds)
19:30:04  <jbergstroem>joaocgreis: i checked that through both init script and through config
19:31:20  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
19:33:19  <jbergstroem>joaocgreis: found it. typo.
19:43:25  * chorrelljoined
19:47:58  * chorrellquit (Client Quit)
20:17:24  * bnoordhuisjoined
20:22:23  * bnoordhuisquit (Ping timeout: 264 seconds)
21:17:27  * node-ghjoined
21:17:28  * node-ghpart
21:18:57  * jgiquit (Quit: jgi)
21:30:38  <thealphanerd>can anyone help me understand a CI failure I'm seeing on raspi?
21:31:17  <thealphanerd>https://ci.nodejs.org/job/node-test-binary-arm/539/RUN_SUBSET=2,nodes=pi1-raspbian-wheezy/tapTestReport/test.tap-81/
21:59:52  * jgijoined
22:22:46  <jbergstroem>thealphanerd: i wonder if the path might be too long
22:22:56  <thealphanerd>it might be
22:23:07  <thealphanerd>it looks like trott had recently landed a commit to make the path even shorter
22:23:17  <thealphanerd>the weirdest bit is v5.3 and master passes
22:23:25  <thealphanerd>it's only the v5.4 line having problems
22:23:30  <jbergstroem>hangon
22:23:35  <thealphanerd>thanks
22:23:38  <jbergstroem>is this recently rebased ?
22:23:55  <jbergstroem>it should be looking for it in NODE_TEMP_DIR=${HOME}/node-tmp
22:24:00  <jbergstroem>but that seems to be the full path
22:26:10  <jbergstroem>hm
22:26:12  <jbergstroem>probably not related
22:26:17  <jbergstroem>but above should actually be NODE_TEST_DIR
22:26:29  <jbergstroem>changing that in all setups and retrying
22:29:54  <thealphanerd>thanks jbergstroem
22:30:11  * node-ghjoined
22:30:12  * node-ghpart
22:30:34  <jbergstroem>thealphanerd: with NODE_TEST_DIR the path is essentially /home/iojs/node-tmp/test.sock
22:30:57  <jbergstroem>sorry, /home/iojs/node-tmp/tmp.$threadid/test.sock
22:31:11  * node-ghjoined
22:31:12  * node-ghpart
22:31:37  <thealphanerd>jbergstroem so is it a CI env problem?
22:31:43  <jbergstroem>i don't think so
22:31:50  <thealphanerd>I didn't either
22:31:50  <jbergstroem>i think it might be path related but i'm not sure
22:31:58  <thealphanerd>it is only failing on that one machine
22:32:02  <thealphanerd>and only on those releases
22:32:11  <jbergstroem>all i know that after I landed my node_test_dir patch i _should've_ added node_test_dir to all jobs and not node_temp_dir
22:32:26  <jbergstroem>(node_test_dir env or --temp-dir flag. urgh)
22:32:48  <jbergstroem>on that one machine probably means on all wheezy arm machines
22:41:10  <jbergstroem>ok, temp dir should be running now
22:41:24  <jbergstroem>i had to export a different home on freebsd otherwise all good
22:47:23  <thealphanerd>ok I'll try again :D
22:50:07  <thealphanerd>https://ci.nodejs.org/job/node-test-commit-arm-fanned/1054/
22:50:26  <jbergstroem>do it!
23:02:22  <thealphanerd>jbergstroem still throwing up on the same issue
23:02:29  <thealphanerd># Error: ENOENT: no such file or directory, chmod '/home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/addons/nodes/pi1-raspbian-wheezy/test/tmp.0/test.sock'
23:15:19  <thealphanerd>jbergstroem is there supposed to be a file test.sock in the tmpdir by default?
23:15:30  <jbergstroem>the test should create one
23:15:59  <thealphanerd>so test.sock is referenced by common.PIPE
23:16:51  <thealphanerd>which AFAIK simply exports exports.PIPE = exports.tmpDir + '/test.sock';
23:17:36  <jbergstroem>yes
23:17:39  <jbergstroem>all good
23:17:45  <jbergstroem>i mitigated long paths by introducing node_test_dir
23:18:08  <jbergstroem>looks like one of the arm jobs still had the wrong environment variable. i've fixed that - so _if_ the test is failing because of long paths it should be fixed now
23:18:25  <thealphanerd>was that fixed prior to the last CI job I ran?
23:18:39  <jbergstroem>no
23:18:43  <jbergstroem>45secs ago
23:18:50  <jbergstroem>you can cancel and go again if you want
23:19:46  <thealphanerd>ok
23:19:48  <thealphanerd>one more run :D
23:19:53  <thealphanerd>thanks again for all the help
23:20:34  <jbergstroem>np :) i've wanted to fix the long path issues for a while
23:21:02  <thealphanerd>https://ci.nodejs.org/job/node-test-commit-arm-fanned/1056/
23:28:20  <jbergstroem>:/ same https://ci.nodejs.org/job/node-test-binary-arm/549/
23:29:50  <jbergstroem>i know i'm passing the correct stuff. i wonder why it still gives the wrong path
23:31:09  <thealphanerd>jbergstroem looking good!
23:31:35  <thealphanerd>oh wait
23:31:40  <thealphanerd>that is a completely different failure
23:31:41  <thealphanerd>afaik
23:31:47  <jbergstroem>oh?
23:32:04  <thealphanerd>it looks like the original failure with path's was fixed
23:32:14  <jbergstroem>Error: listen EADDRINUSE /home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/addons/nodes/pi2-raspbian-wheezy/test/tmp.0/test.sock
23:32:25  <thealphanerd>but that's EADDRINUSE
23:32:37  <thealphanerd>whereas before we were getting ENOENT
23:32:43  <thealphanerd>and it's on a different machine
23:32:49  <jbergstroem>sure but the path is still wrong for node_test_dir
23:33:57  <thealphanerd>ahh
23:34:09  <thealphanerd>should I hold off before running CI again?
23:42:07  * Fishrock123quit (Quit: Leaving...)
23:49:41  <jbergstroem>i'm not doing anything at the moment
23:49:56  <jbergstroem>hopefully the run you started for some reason didn't incorporate my config save or something
23:54:21  <jbergstroem>thealphanerd: ok, this makes more sense: Error: EXDEV: cross-device link not permitted, link '/home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/0/nodes/pi1-raspbian-wheezy/test/fixtures/cycles/root.js' -> '/home/iojs/node-tmp/tmp.0/link1.js'
23:54:38  <jbergstroem>i wonder how its symlinked there
23:54:46  <jbergstroem>i'll have a look
23:55:32  <jbergstroem>ah; the entire build directory is nfs'ed