00:11:18  * node-ghjoined
00:11:18  * node-ghpart
00:18:55  * evanlucasquit (Read error: Connection reset by peer)
00:19:21  * evanlucasjoined
00:23:56  * node-ghjoined
00:23:56  * node-ghpart
00:25:49  * jgiquit (Quit: jgi)
00:27:14  * jgijoined
00:50:33  * node-ghjoined
00:50:33  * node-ghpart
01:23:45  * Fishrock123quit (Quit: Leaving...)
02:14:32  * node-ghjoined
02:14:32  * node-ghpart
02:24:54  * node-ghjoined
02:24:55  * node-ghpart
02:26:17  * jgiquit (Quit: jgi)
02:29:46  <rvagg>jbergstroem: http://www.ansible.com/blog/ansible-2.0-launch
02:29:55  <jbergstroem>rvagg: yep! on it
02:46:06  * node-ghjoined
02:46:07  * node-ghpart
02:48:57  * node-ghjoined
02:48:57  * node-ghpart
02:50:09  * node-ghjoined
02:50:10  * node-ghpart
03:17:04  * evanlucasquit (Read error: Connection reset by peer)
03:18:17  * evanlucasjoined
03:20:54  * node-ghjoined
03:20:54  * node-ghpart
03:55:49  * chorrelljoined
04:21:37  * node-ghjoined
04:21:37  * node-ghpart
04:22:59  * node-ghjoined
04:22:59  * node-ghpart
04:28:21  * node-ghjoined
04:28:22  * node-ghpart
04:56:44  * jgijoined
05:09:33  * evanluca_joined
05:10:32  * evanlucasquit (Read error: Connection reset by peer)
05:14:11  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
06:12:58  * trottjoined
06:14:05  <trott>Hello, build friends. Any chance the repeated failures the last few hours on Windows CI is build infra related and not a regression that's slipped in?
06:14:30  <trott>https://ci.nodejs.org/job/node-test-binary-windows/566/RUN_SUBSET=1,VS_VERSION=vs2015,label=win10/tapTestReport/test.tap-73/
06:15:21  <trott>https://ci.nodejs.org/job/node-test-binary-windows/569/RUN_SUBSET=1,VS_VERSION=vs2015,label=win10/tapTestReport/test.tap-171/
06:15:29  <trott>https://ci.nodejs.org/job/node-test-binary-windows/568/RUN_SUBSET=1,VS_VERSION=vs2015,label=win10/tapTestReport/test.tap-171/
06:15:35  <trott>https://ci.nodejs.org/job/node-test-binary-windows/567/RUN_SUBSET=1,VS_VERSION=vs2015,label=win10/tapTestReport/test.tap-171/
06:16:11  <trott>(First link above might be unrelated, but I'm definitely talking about those last three. Could totally be a regression, I'm just hoping not. :-/ )
06:33:16  <jbergstroem>hm
06:33:32  <jbergstroem>afaik we've done no changes to infra
06:34:50  * trottquit (Ping timeout: 260 seconds)
06:43:16  * trottjoined
06:48:54  * trottquit (Read error: Connection reset by peer)
06:49:10  * trottjoined
06:49:57  * jgiquit (Quit: jgi)
07:28:54  <trott>Never mind, it's looking more and more like the test failures are not spurious...
07:37:50  * trottquit (Quit: leaving)
07:52:29  <jbergstroem>"good"
08:14:16  * node-ghjoined
08:14:16  * node-ghpart
08:15:51  * node-ghjoined
08:15:51  * node-ghpart
09:06:29  * node-ghjoined
09:06:29  * node-ghpart
09:33:41  * rmgquit (Remote host closed the connection)
10:18:33  * imjacobclarkjoined
11:05:34  * rmgjoined
11:10:50  * rmgquit (Ping timeout: 272 seconds)
11:19:13  * node-ghjoined
11:19:14  * node-ghpart
11:24:03  * node-ghjoined
11:24:03  * node-ghpart
11:28:07  * node-ghjoined
11:28:08  * node-ghpart
11:40:02  * node-ghjoined
11:40:02  * node-ghpart
12:03:42  * imjacob__joined
12:03:42  * imjacobclarkquit (Remote host closed the connection)
12:05:37  * imjacobclarkjoined
12:05:38  * imjacob__quit (Remote host closed the connection)
12:10:34  * imjacobclarkquit (Remote host closed the connection)
12:11:03  * imjacobclarkjoined
12:14:19  * imjacobc_joined
12:14:20  * imjacobclarkquit (Remote host closed the connection)
12:56:34  * imjacobc_quit (Remote host closed the connection)
12:56:55  * imjacobclarkjoined
12:58:18  * imjacobclarkquit (Remote host closed the connection)
12:59:03  * imjacobclarkjoined
13:06:45  * rmgjoined
13:11:34  * rmgquit (Ping timeout: 256 seconds)
13:47:31  * node-ghjoined
13:47:32  * node-ghpart
14:30:48  * chorrelljoined
15:14:58  * node-ghjoined
15:14:59  * node-ghpart
16:06:30  * imjacobclarkquit (Ping timeout: 260 seconds)
16:08:21  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:17:23  * Fishrock123joined
16:20:23  * imjacobclarkjoined
16:20:44  * imjacobclarkquit (Client Quit)
16:21:50  * bnoordhuisjoined
16:23:17  * rmgjoined
16:24:06  * imjacobclarkjoined
16:26:21  * chorrelljoined
16:28:03  * rmgquit (Ping timeout: 265 seconds)
16:36:55  * evanluca_quit (Read error: Connection reset by peer)
16:37:54  * evanlucasjoined
16:53:57  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:56:33  * jgijoined
17:05:10  * jgiquit (Quit: jgi)
17:05:27  * rmgjoined
17:09:07  * trottjoined
17:29:17  * jgijoined
17:31:18  * imjacobclarkquit
17:32:36  * bnoordhuisquit (Ping timeout: 264 seconds)
17:33:43  * bnoordhuisjoined
17:46:52  * jgiquit (Quit: jgi)
18:07:56  * bnoordhuisquit (Ping timeout: 276 seconds)
18:08:37  * joaocgreisquit (K-Lined)
18:08:37  * rvaggquit (K-Lined)
18:08:46  * starefossenquit (K-Lined)
18:08:48  * bretquit (K-Lined)
18:08:48  * orangemochaquit (K-Lined)
18:08:48  * michael___quit (K-Lined)
18:11:23  * bretjoined
18:17:13  * bnoordhuisjoined
18:18:28  * joaocgreisjoined
18:19:55  * rvaggjoined
18:22:41  * orangemochajoined
18:28:18  * starefossenjoined
18:29:32  * michael___joined
18:30:45  * jgijoined
18:46:36  * chorrelljoined
18:48:22  * node-ghjoined
18:48:22  * node-ghpart
18:54:26  * bnoordhuisquit (Ping timeout: 272 seconds)
19:06:01  * rmgquit
19:16:13  <michael___>Should I talk to Rodd in the build channel about fedora 20 ?
19:18:11  <jbergstroem>your call, you know ppc better than us
19:18:38  <jbergstroem>so, should i stick with fedora20 for ppc_be and ubuntu14 for ppc_le?
19:19:22  <michael___>Sorry posted that in wrong channel, but to respond in case people see the original
19:19:39  <jbergstroem>gotcha
19:19:47  <michael___>I'd prefer to stick with fedora20 so that we have support for earlier OS's
19:54:04  * bnoordhuisjoined
19:54:51  * node-ghjoined
19:54:52  * node-ghpart
19:57:14  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
20:32:06  <trott>Is there any way to run a stress test on a commit hash rather than a reference? That would be super useful right now…
20:51:22  <jbergstroem>joaocgreis: ^
21:00:58  * chorrelljoined
21:02:33  <joaocgreis>trott: not that I know of.. It needs the reference to avoid fetching everything, but I guess I can change if it would help you
21:05:06  <joaocgreis>You can use git init locally followed by the fetch that appears in the job console to try refs and get exactly what the job gets
21:11:11  * jgiquit (Quit: jgi)
21:12:55  <trott>I guess the easiest thing to do probably is just tag the commits I want to test and use that reference. I've also been doing a lot of create-a-branch-at-the-state-I-want-to-test. But that balloons into a lot of branches surprisingly fast. On the other hand, branches are cheap....
21:13:35  * bnoordhuisquit (Ping timeout: 240 seconds)
21:26:20  <jbergstroem>trott: i usually do a ton of branching as well. turns out its usually the easiest way, rebasing on top of different stuff, merging other stuff in etc
21:47:39  * bnoordhuisjoined
21:47:55  * jgijoined
21:52:22  * bnoordhuisquit (Ping timeout: 265 seconds)
22:14:58  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:17:52  * bnoordhuisjoined
22:22:21  <jbergstroem>joaocgreis: is there a way to have a jenkins job selectively choose which slaves to run on based on for instance a label or a shell expression?
22:25:08  * bnoordhuisquit (Ping timeout: 246 seconds)
22:36:28  * trottpart
22:42:47  <joaocgreis>jbergstroem: the best I found is in the stress test job. The combination filter is a groovy expression, but actually quite limited because of security. It could be quite powerful if you figure out how to unlimit it
22:42:57  <jbergstroem>ok
22:50:25  <jbergstroem>is the combination filter a bash expression?
22:54:25  <joaocgreis>Groovy
22:55:21  <joaocgreis>kind of Java coffeescript from what I understood
22:55:42  <jbergstroem>great. another language to pick up
22:56:29  * bnoordhuisjoined
22:59:48  <jbergstroem>was hoping to select smartos13/15 depending on if we're building <1.0 or >1.0 for iojs-release
23:01:12  * bnoordhuisquit (Ping timeout: 255 seconds)
23:19:44  <joaocgreis>There's already something like that, test-pr or test-commit have some code to select the tests subset
23:40:18  <jbergstroem>we just had our first green run (disregarding the known windows failures) for parallel tests: https://ci.nodejs.org/job/node-test-commit/1731/
23:40:53  <jbergstroem>some platforms get significant speed increases while other known platforms still needs work in other areas
23:43:08  * jgiquit (Quit: jgi)
23:44:09  * jgijoined
23:52:52  * node-ghjoined
23:52:52  * node-ghpart