00:41:55  * jgiquit (Quit: jgi)
01:19:09  * rmgjoined
01:23:51  * rmgquit (Ping timeout: 255 seconds)
01:34:22  * Fishrock123quit (Ping timeout: 256 seconds)
02:08:02  <jbergstroem>First build through our CI with parallel tests enabled: https://ci.nodejs.org/job/node-test-commit-linux/nodes=centos5-32/1621/
02:08:27  <jbergstroem>sorry, https://ci.nodejs.org/job/node-test-commit/1561/
02:20:38  <jbergstroem>just as an indication: osx: 5m20s -> 3m6s, freebsd: 6m19s -> 4m53s, plinux: 8m29s -> 6m14s (failed)
02:20:55  <jbergstroem>the rest isn't really measurable since there's an incurred delay in waiting for some subtasks
02:21:18  <jbergstroem>but the parallelism at least seems to be ~30-40% increase (one to at least two cores)
02:22:00  <jbergstroem>smartos64 is for instance 9min -> 5min
02:23:01  <jbergstroem>i'll have a quick chat with trott about the state of running tests in parallel. hopefully we can get that into base shortly
04:14:10  * jgijoined
04:47:18  * trottjoined
04:48:22  * jgiquit (Quit: jgi)
04:49:40  * trottquit (Client Quit)
05:19:00  * trottjoined
05:49:46  * trottquit (Quit: leaving)
07:17:57  * bnoordhuisjoined
07:21:19  * rmgjoined
07:26:06  * rmgquit (Ping timeout: 255 seconds)
07:35:54  * bnoordhuisquit (Ping timeout: 256 seconds)
07:39:21  * bnoordhuisjoined
08:44:04  * bnoordhuisquit (Ping timeout: 272 seconds)
09:49:45  * bnoordhuisjoined
09:54:47  * bnoordhuisquit (Ping timeout: 264 seconds)
11:22:59  * rmgjoined
11:28:06  * rmgquit (Ping timeout: 272 seconds)
11:39:38  * bnoordhuisjoined
12:51:48  * node-ghjoined
12:51:48  * node-ghpart
12:54:49  * node-ghjoined
12:54:49  * node-ghpart
12:57:48  * bnoordhuisquit (Ping timeout: 264 seconds)
13:23:42  * rmgjoined
13:28:22  * rmgquit (Ping timeout: 256 seconds)
14:03:21  * bnoordhuisjoined
14:08:25  * bnoordhuisquit (Ping timeout: 260 seconds)
15:05:05  * bnoordhuisjoined
15:05:55  * joaocgreisquit (Ping timeout: 240 seconds)
15:07:15  * joaocgreisjoined
15:24:26  * rmgjoined
15:29:05  * rmgquit (Ping timeout: 246 seconds)
15:31:08  * bnoordhuisquit (Ping timeout: 276 seconds)
16:01:19  * bnoordhuisjoined
16:25:12  * rmgjoined
16:29:44  * rmgquit (Ping timeout: 245 seconds)
17:27:59  * jgijoined
17:43:33  * jgiquit (Quit: jgi)
17:47:04  * jgijoined
17:50:18  * jgiquit (Client Quit)
18:10:08  * jgijoined
18:14:12  * jgiquit (Client Quit)
18:30:03  * jgijoined
18:30:37  * rmgjoined
19:36:33  * trottjoined
19:37:59  <trott>Lately, I've been stress testing a bunch of tests that are only flaky on the Microsoft Azure hosts but not on the Rackspace Windows hosts. The way I've been doing this is I start a stress test (usually selecting win2012r2 from the RUN_LABEL menu) and wait to see whether it went to a Microsoft host or a Rackspace host. If it went to a Rackspace host, I cancel and try again.
19:38:26  <trott>Is there a way (perhaps selecting a different run label?) that I can get one or the other every single time rather than having it be luck of the draw?
19:41:28  * bnoordhuisquit (Ping timeout: 272 seconds)
19:44:11  * bnoordhuisjoined
20:06:06  * trottquit (Ping timeout: 240 seconds)
20:30:00  * jgiquit (Quit: jgi)
20:33:01  * jgijoined
20:38:46  * Fishrock123joined
20:42:39  * jgiquit (Quit: jgi)
21:05:14  * jgijoined
21:13:00  * jgiquit (Quit: jgi)
21:32:16  * jgijoined
21:45:20  * jgiquit (Quit: jgi)
22:05:55  * bnoordhuisquit (Ping timeout: 260 seconds)
23:12:10  * bnoordhuisjoined
23:17:26  * bnoordhuisquit (Ping timeout: 272 seconds)
23:41:28  * linkn3echojoined
23:42:43  * jgijoined