00:26:24  <Trott>I mentioned this in an issue where I @-mentioned the build team, but I'm going to ask here as well anyway: Any chance we can get the POST_STATUS_TO_PR checkbox on by default? Doesn't seem like there's a reason to leave it unchecked in any of the typical scenarios where someone is using the job, is there?
00:27:56  <jbergstroem>Trott: soon young padawan
00:28:00  <jbergstroem>still in testing
00:28:18  <jbergstroem>we have some work to do as well
00:50:37  <jbergstroem>joaocgreis: you working with the win slaves?
00:54:43  <joaocgreis>jbergstroem: no. They just die. This started about one week ago, don't know why
00:55:51  <jbergstroem>i was thinking software updates or smth
00:56:05  <jbergstroem>is it a reboot or just slave dying?
00:58:08  <joaocgreis>I've seen both, plus shutdown (has to log in to rackspace some times to bring slaves back)
00:58:45  <joaocgreis>these two -1 and -8 that just died are online, apparently only jenkins died
00:59:34  <joaocgreis>the strange thing is that jenkins runs from a bat file, called in an infinite loop, so I don't know how it managed to take cmd down with it
01:04:15  <joaocgreis>master seems slower than usual
01:05:50  * Fishrock123joined
01:10:50  * node-ghjoined
01:10:50  * node-ghpart
01:24:53  <jbergstroem>joaocgreis: i ran into the login isssue the other day too
01:25:26  <jbergstroem>the second i logged on remote desktop it spawned jenkins
01:25:27  <jbergstroem>strange
01:46:11  * Fishrock123quit (Quit: Leaving...)
03:37:38  <Trott>OK, this one looks more workspace related, I think. At least the word "workspace" appears: c:\workspace\node-compile-windows\label\win-vs2015>TASKKILL /F /IM node.exe /T || TRUE
03:37:38  <Trott>ERROR: The process "node.exe" not found.
03:37:38  <Trott>c:\workspace\node-compile-windows\label\win-vs2015>TASKKILL /F /IM run-tests.exe /T || TRUE
03:37:38  <Trott>ERROR: The process "run-tests.exe" not found.
03:37:43  <Trott>https://ci.nodejs.org/job/node-compile-windows/3633/label=win-vs2015/console
03:38:06  <Trott>Same/similar here: https://ci.nodejs.org/job/node-compile-windows/3633/label=win-vcbt2015/console
05:06:35  <jbergstroem>Trott: i don't think thats the culprit -- that's basically reaping any trailing processes no?
05:23:42  <thealphanerd>supppp ljharb
05:27:00  <ljharb>yo yo
05:28:49  <ljharb>so what i'm working on now is, being able to cache and reuse downloaded tarballs
05:29:06  <ljharb>which should enable travis to cache that directory, and that should mean successive tests get to skip all the download time
05:29:19  <ljharb>and i'm hoping that gain is enough to allow the iojs source build tests to pass without timing out
05:43:22  * joaocgreis_joined
05:48:38  * joaocgreisquit (Ping timeout: 250 seconds)
05:49:14  * joaocgreis_changed nick to joaocgreis
10:52:59  * thealphanerdquit (Quit: farewell for now)
10:53:29  * thealphanerdjoined
11:25:20  * node-ghjoined
11:25:20  * node-ghpart
11:50:04  * jenkins-monitorquit (Excess Flood)
11:50:13  * jenkins-monitorjoined
12:33:42  * node-ghjoined
12:33:42  * node-ghpart
12:45:49  * node-ghjoined
12:45:49  * node-ghpart
12:46:39  * node-ghjoined
12:46:39  * node-ghpart
13:13:29  * node-ghjoined
13:13:29  * node-ghpart
13:24:20  * Fishrock123joined
13:36:09  * lance|afkchanged nick to lanceball
14:15:06  * lanceballchanged nick to lance|afk
14:32:42  * lance|afkchanged nick to lanceball
16:28:16  * node-ghjoined
16:28:16  * node-ghpart
17:23:04  * node-ghjoined
17:23:04  * node-ghpart
18:40:26  * node-ghjoined
18:40:26  * node-ghpart
18:51:50  * chorrelljoined
19:24:22  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
19:38:47  * node-ghjoined
19:38:47  * node-ghpart
19:47:36  * node-ghjoined
19:47:36  * node-ghpart
19:49:11  * node-ghjoined
19:49:11  * node-ghpart
20:13:38  * node-ghjoined
20:13:38  * node-ghpart
20:21:19  <joaocgreis>flaky tests are not working in CI, jobs where flaky tests fail are green and not yellow. Anyone knows why? (jbergstroem? rvagg?)
20:21:38  <jbergstroem>should be 'unstable' right?
20:22:33  <jbergstroem>i found a native alpine34 image at joyent
20:22:40  <jbergstroem>was thinking we could use that instead of messing aroudn with docker?
20:23:09  <jbergstroem>currently running the libuv build/test suite: https://ci.nodejs.org/view/libuv/job/libuv-test-commit-linux/96/nodes=alpine34-x64/console
20:23:40  <joaocgreis>yes, they should be marked unstable..
20:24:23  <jbergstroem>i can have a loook in a bit
20:24:26  <jbergstroem>just want to finish this
21:22:51  <jbergstroem>joaocgreis: looks like fanned has skipped? https://ci.nodejs.org/job/node-test-commit-windows-fanned/
21:26:33  <jbergstroem>i think our pr scripts won't update properly
21:26:53  <jbergstroem>i only have access to success/fail; need to make it more complicated to expose unstable :(
21:41:43  * lanceballchanged nick to lance|afk
21:57:34  * node-ghjoined
21:57:34  * node-ghpart
22:06:11  <Trott>Looks like the "post status to PR" thing posts AIX as failed (sometimes? all the time? ) when AIX actually succeeds. See current status on https://github.com/nodejs/node/pull/8073 and compare to the results at https://ci.nodejs.org/job/node-test-commit-aix/344/. /cc mhdawson joaocgreis jbergstroem I guess?
22:11:27  * node-ghjoined
22:11:27  * node-ghpart
23:54:43  * Fishrock123quit (Remote host closed the connection)