00:04:19  <jbergstroem>thealphanerd: you either successfully reverted or jenkins has some kind of memory state I don't fully understand
00:04:35  * trott1part
00:04:35  <thealphanerd>I think I missed one thing
00:04:37  <jbergstroem>i know it stores stuff in memory but are pretty sure changes are serialized on save
00:04:53  <thealphanerd>I think I missed putting in the check for flaky tests
00:06:01  <jbergstroem>:'((((( the backup job ran 20 mins ago
00:06:47  <jbergstroem>ok don't worry i'll have a look manually then
00:06:49  <thealphanerd>does it keep multiple back ups
00:07:02  <thealphanerd>I compared it to the linux and smartos jobs
00:07:34  <thealphanerd>I'm 90% this is back to where it was. I only changed the execute shell that was running make
00:08:14  <jbergstroem>the flaky part looks ok
00:08:21  <jbergstroem>no; we back up the folder manually
00:08:37  <jbergstroem>if we decided to shrink the logs I could rsnapshot our backup
00:21:45  * node-ghjoined
00:21:46  * node-ghpart
00:23:22  * node-ghjoined
00:23:23  * node-ghpart
00:25:36  * bnoordhuisjoined
00:30:27  * bnoordhuisquit (Ping timeout: 260 seconds)
00:31:02  <thealphanerd>jbergstroem so is there a way to check that all is well?
00:31:40  * chorrelljoined
00:32:04  <jbergstroem>thealphanerd: well it depends since i don't really know what you changed. Just run a few builds
00:32:25  <thealphanerd>will do
00:41:50  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
01:11:35  <thealphanerd>https://ci.nodejs.org/job/thealphanerd-smoker/nodes=debian8-64/2/console
01:11:35  <thealphanerd>woot
01:11:39  <thealphanerd>smoketester is working :D
01:14:11  <thealphanerd>spoke too soon
01:14:12  <thealphanerd>womp
01:59:31  * jgiquit (Quit: jgi)
02:49:39  * jgijoined
02:57:08  * node-ghjoined
02:57:08  * node-ghpart
03:04:17  <thealphanerd>jbergstroem I ran CI on the head of every major release for osx and all seems to be fine
03:06:23  * jgiquit (Quit: jgi)
03:27:32  * jgijoined
03:31:43  * jgiquit (Client Quit)
04:28:22  * Fishrock123quit (Quit: Leaving...)
04:37:35  * rmgquit (Remote host closed the connection)
04:38:08  * rmgjoined
04:42:37  * rmgquit (Ping timeout: 265 seconds)
05:06:43  * jgijoined
05:10:22  * jgiquit (Client Quit)
05:35:18  <rvagg>this sucks, bad https://github.com/nodejs/node/issues/4531
05:38:06  * jgijoined
05:44:14  * jgiquit (Quit: jgi)
05:54:36  <rvagg>currently revisiting my gcc 4.9 instructions @ https://github.com/nodejs/build/tree/master/setup/debian-wheezy-gcc to see if I can get it to compile on a newly provisioned wheezy scaleway machine, I think last time I tried this I had limited success
05:59:40  * jgijoined
06:25:45  * jgiquit (Quit: jgi)
07:39:26  * rmgjoined
07:43:54  * rmgquit (Ping timeout: 245 seconds)
07:58:11  * evanlucasquit (Read error: Connection reset by peer)
07:59:10  * evanlucasjoined
08:21:02  * node-ghjoined
08:21:02  * node-ghpart
08:21:14  * node-ghjoined
08:21:14  * node-ghpart
08:41:26  * node-ghjoined
08:41:27  * node-ghpart
08:42:56  * node-ghjoined
08:42:57  * node-ghpart
08:53:12  * node-ghjoined
08:53:12  * node-ghpart
09:40:14  * bnoordhuisjoined
09:59:37  * imjacobclarkjoined
10:39:00  * imjacobclarkquit (Ping timeout: 260 seconds)
10:40:22  * imjacobclarkjoined
11:09:23  * bnoordhuisquit (Ping timeout: 276 seconds)
11:09:58  * imjacobclarkquit (Ping timeout: 256 seconds)
11:10:36  * bnoordhuisjoined
11:41:08  * rmgjoined
11:45:58  * rmgquit (Ping timeout: 272 seconds)
12:05:14  <joaocgreis>jbergstroem, orangemocha: the problem with git clean seems to be that some test creates a temporary file with a very long path. rm bundled with git seems to be able to clean it, i'll add it to the end of the job
13:41:42  * rmgjoined
13:46:22  * rmgquit (Ping timeout: 256 seconds)
13:56:21  * evanlucasquit (Quit: Textual IRC Client: www.textualapp.com)
13:58:58  * evanlucasjoined
14:10:18  * chorrelljoined
15:30:37  * chorrellquit (Read error: Connection reset by peer)
15:31:16  * chorrelljoined
15:42:30  * rmgjoined
15:47:12  * rmgquit (Ping timeout: 250 seconds)
16:00:56  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
16:09:16  * Fishrock123joined
16:21:22  * evanlucasquit (Quit: Textual IRC Client: www.textualapp.com)
16:22:59  * evanluca_joined
16:25:45  * jgijoined
16:26:08  * bnoordhuisquit (Ping timeout: 246 seconds)
16:33:36  * jgiquit (Quit: jgi)
16:34:44  * Fishrock123quit (Remote host closed the connection)
16:37:31  * Fishrock123joined
16:41:31  * jgijoined
16:48:16  * jgiquit (Quit: jgi)
16:51:25  * Fishrock123quit (Remote host closed the connection)
16:58:42  * rmgjoined
17:16:13  * bnoordhuisjoined
17:17:19  * jgijoined
17:21:19  * jgiquit (Client Quit)
17:52:17  * Fishrock123joined
17:53:57  * jgijoined
17:57:00  * Fishrock123quit (Ping timeout: 255 seconds)
18:00:51  * node-ghjoined
18:00:52  * node-ghpart
18:10:02  * Fishrock123joined
18:30:56  <thealphanerd>rvagg I'm getting some seriously weird errors on CITGM in CI. Would you have some time to help debug (open invite to anyone else adventurous enough)
18:30:56  <thealphanerd>https://ci.nodejs.org/job/thealphanerd-smoker/nodes=ubuntu1504-64/9/console
19:11:14  <joaocgreis>rvagg: can I land https://github.com/nodejs/build/pull/286 ? Is there some procedure to update the server or is it automatic?
19:17:14  * node-ghjoined
19:17:14  * node-ghpart
19:23:09  * node-ghjoined
19:23:10  * node-ghpart
19:23:27  * node-ghjoined
19:23:27  * node-ghpart
21:39:02  * jgiquit (Quit: jgi)
22:17:44  <jbergstroem>joaocgreis: ok
22:17:46  <jbergstroem>thealphanerd: we all good regarding the osx job?
22:18:22  <thealphanerd>jbergstroem I believe so
22:18:44  <jbergstroem>great
22:19:02  <thealphanerd>and I've been working with Tim Oxly today to try and get the smoker CI stuff working
22:25:08  * jgijoined
22:36:53  <jbergstroem>i think i'll add another debian8 machine so we don't get held up
22:36:55  <jbergstroem>we only have one
22:37:30  <jbergstroem>perhaps im not reading this properly; which machines do you smoketest on?
22:38:36  <jbergstroem>ubuntu1504 gotcha
22:39:56  <thealphanerd>I switched
22:40:12  <thealphanerd>but the hope would be to eventually do it against a matrix of machines
22:42:38  <jbergstroem>yep all good
22:42:50  <jbergstroem>esp represent multiple os'es i reckon
22:43:01  <jbergstroem>how long is a run on one vm (ish)?
22:44:18  <rvagg>thealphanerd: I'm taking a couple of days with the family so don't have time for a deep-dive on anything. If you can't get help in here perhaps open an issue in build to discuss?
22:44:33  <thealphanerd>sgtm
22:44:36  <thealphanerd>have fun with the fam!
22:44:41  <thealphanerd>thanks for heads up
22:44:50  <thealphanerd>smoker is working
22:44:51  <thealphanerd>https://ci.nodejs.org/job/thealphanerd-smoker-too/nodes=ubuntu1504-64/8/console
22:45:08  <thealphanerd>just have to chase down a bug in socker.io
23:07:25  * node-ghjoined
23:07:25  * node-ghpart
23:08:41  <michael___>orangemocha I'm wondering if you know the history as to why the non-installer download for windows is a simple binary as opposed to a zip with the binary, npm etc which would be closer to what you get on other platforms with the tar.gz
23:32:42  * trottjoined
23:42:57  <jbergstroem>thealphanerd: awesome. I'm keen on exploring getting tap output from that run. Possbly just a super simple fail/pass and collect - but it would be easier to hook up to a job forward
23:43:50  <thealphanerd>jbergstroem I was actually just thinking about that yesterday. Should not be too difficult to modify citgm to output tap.
23:44:22  <jbergstroem>thealphanerd: at a minimum, just collect the amount of jobs (1...16) then output ok/not ok for each run
23:44:37  <jbergstroem>thealphanerd: with tap 13 you can be a bit more verbose should you want to (bubble up errors)
23:46:46  * bnoordhuisquit (Ping timeout: 240 seconds)