00:01:03  <jbergstroem>54G ./node-test-binary-windows
00:01:06  <jbergstroem>:'[
00:05:15  <mscdex>jbergstroem: still no dice. it starts, but the job immediately finishes and the job status page doesn't show the right target
00:05:21  <jbergstroem>hm
00:05:23  <jbergstroem>thanks
00:05:28  <jbergstroem>got a link handy?
00:05:41  <mscdex>https://ci.nodejs.org/job/node-stress-single-test/1082/
00:06:44  <jbergstroem>joaocgreis: 26G ./.git in /var/lib/jenkins/jobs/node-test-binary-windows/workspace
00:06:54  <jbergstroem>i'll run a gc now
00:06:59  <jbergstroem>but do we need to cron that stuff?
00:08:21  <jbergstroem>and it died!!
00:08:51  <jbergstroem>mscdex: found the issue
00:10:02  * jenkins-monitorquit (Remote host closed the connection)
00:10:10  * jenkins-monitorjoined
00:12:48  * mscdexquit (Ping timeout: 258 seconds)
00:14:52  <jbergstroem>30 more secs
00:14:53  <jbergstroem>sorry
00:15:01  * jenkins-monitorquit (Remote host closed the connection)
00:15:02  <jbergstroem>if this launches again it'll just die anyway
00:15:11  * jenkins-monitorjoined
00:27:30  * mscdexjoined
00:32:41  <jbergstroem>mscdex: seems to be working now
00:33:33  <mscdex>jbergstroem: yep, thanks!
01:13:37  * rmgquit (Remote host closed the connection)
01:31:58  * rmgjoined
01:35:50  * not-an-aardvarkjoined
01:45:29  * chorrelljoined
01:51:15  <joaocgreis>jbergstroem: workspace again :( I don't know how the .git gets to that state nor how to clean the workspace automatically making sure it's not in use
01:51:32  <joaocgreis>thanks for adding the host to stesstest btw
01:51:51  <jbergstroem>i've fixed it
01:52:05  <jbergstroem>by removing the big-ass repo and copying the smallest version
01:52:24  <joaocgreis>smallest version?
01:52:34  <jbergstroem>yeah there's multiple versions of hte workspace
01:52:39  <jbergstroem>basically different checkouts
01:52:47  <joaocgreis>ah, don't worry, it'll grow again
01:52:49  <jbergstroem>so i deleted the one that was 16G and copied the one that was 1.6G
01:52:52  <jbergstroem>yes
01:53:08  <jbergstroem>problem is that when git gc launches against the big one java dies
01:53:56  <joaocgreis>copying saves some time in the next run, but in a hurry you can just delete the workspace folder and jenkins will create it
01:54:20  <jbergstroem>tru
01:54:22  <jbergstroem>thats what we should do
01:54:43  <joaocgreis>other workspaces do not grow, it's only that windows one and I don't know why
01:55:15  <joaocgreis>job config looks similar :s
02:00:25  <joaocgreis>Trott: if you want to add labels to the stress test job it should be easy: just open the config, go to Configuration Matrix and tick under labels. Then scroll up and add the exact label name in the big list for the Choice Parameter RUN_LABEL (copy-paste). I'm still happy to add them for you and keep the job working, just mention me here when you need!
02:22:22  * mscdexpart ("Leaving")
02:33:07  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
02:57:46  * imyllerjoined
03:12:25  * imyllerquit (Quit: My iMac has gone to sleep. ZZZzzz…)
04:40:24  <Trott>đź‘Ť
04:54:25  * rmgquit (Remote host closed the connection)
05:14:43  * rmgjoined
05:19:29  * rmgquit (Ping timeout: 268 seconds)
05:24:16  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
05:30:52  * not-an-aardvarkjoined
05:42:03  * rmgjoined
05:46:41  * rmgquit (Ping timeout: 258 seconds)
06:08:55  * rmgjoined
06:13:45  * rmgquit (Ping timeout: 268 seconds)
06:36:12  * rmgjoined
06:39:44  * imyllerjoined
06:40:44  * rmgquit (Ping timeout: 258 seconds)
06:50:08  * imyllerquit (Quit: My iMac has gone to sleep. ZZZzzz…)
07:03:06  * rmgjoined
07:08:01  * rmgquit (Ping timeout: 268 seconds)
07:30:17  * rmgjoined
07:34:47  * rmgquit (Ping timeout: 258 seconds)
07:55:20  * imyllerjoined
08:41:30  * sxaquit (Ping timeout: 265 seconds)
08:46:29  * sxajoined
09:18:23  * node-ghjoined
09:18:23  * node-ghpart
09:18:43  * node-ghjoined
09:18:43  * node-ghpart
09:25:10  * node-ghjoined
09:25:10  * node-ghpart
09:34:16  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
10:49:24  * node-ghjoined
10:49:25  * node-ghpart
11:25:09  * thealphanerdquit (Quit: farewell for now)
11:25:39  * thealphanerdjoined
12:17:13  * node-ghjoined
12:17:13  * node-ghpart
12:28:33  * rmgjoined
12:33:01  * rmgquit (Ping timeout: 258 seconds)
14:18:02  <italoacasas>I think the CI failure is not related with the test, can someone confirm ?
14:18:03  <italoacasas>https://github.com/nodejs/node/pull/10319
14:29:55  * chorrelljoined
14:32:37  <jbergstroem>italoacasas: yeah, can confirm. not sure what happened though
14:33:48  <jbergstroem>intermittent connection issues, it seems
14:39:54  * node-ghjoined
14:39:55  * node-ghpart
14:49:56  <italoacasas>ty
15:06:31  <rvagg>jbergstroem, joaocgreis we didn't get a smartos x64 binary for v0.12.18 just now and I have no idea why. Has anything changed in the last month with smartos for releases? Perhaps that smartos/sunos stuff? These build on the old smartos13 machines, should we have both an x64 and x86 in there? I don't recall. It worked for 0.12.17 tho.
15:07:14  <jbergstroem>I haven't changed anything (I remember)
15:07:26  <jbergstroem>*I can remember
15:09:18  <jbergstroem>https://ci-release.nodejs.org/job/iojs+release/nodes=smartos13-release/1405/console
15:45:22  * imyllerquit (Quit: My iMac has gone to sleep. ZZZzzz…)
16:17:13  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
16:52:39  * lanceballchanged nick to lance|afk
17:18:22  * rmgjoined
19:05:54  * jenkins-monitorquit (Remote host closed the connection)
19:06:05  * jenkins-monitorjoined
19:55:36  * jenkins-monitorquit (Remote host closed the connection)
19:55:48  * jenkins-monitorjoined
20:43:41  * jenkins-monitorquit (Remote host closed the connection)
20:43:52  * jenkins-monitorjoined
20:45:15  * imyllerjoined
20:49:13  <joaocgreis> rvagg I did not change anything there. Did you solve it?
20:50:29  <joaocgreis>jbergstroem: that link seems to be to v7.3 release. I think v0.12 was the next one, 1406: https://ci-release.nodejs.org/job/iojs+release/1406/nodes=smartos13-release/console after uploading it ends with: make: *** No rule to make target ` '. Stop.
20:58:20  <joaocgreis>(i meant after uploading x84)
20:58:36  <joaocgreis>x86
23:20:26  <rvagg>am going to try build 0.12.18 again and see if anything changes, I'm still scratching my head at how x86 builds worked previously, I thought we had a server each for x64 and x86 but current config doesn't show that