04:48:05  * node-slack-botpart
04:48:17  * node-slack-botjoined
05:54:27  * lanceball_joined
05:55:51  * lanceballquit (*.net *.split)
07:55:31  * node-ghjoined
07:55:31  * node-ghpart
10:22:02  * sxajoined
15:20:37  * sxaquit (Remote host closed the connection)
15:21:32  * sxajoined
16:39:26  * lanceball_quit (Excess Flood)
16:40:42  * lanceballjoined
16:49:52  * lanceballquit (Changing host)
16:49:52  * lanceballjoined
17:15:16  <Trott>I *think* I'm noticing that Windows flaky tests tend to fail on Azure a lot more (or even exclusively in some cases?) than on Rackspace. Is it possible that our Azure machines are slower or have less memory or whatever than our Rackspace hosts? Is it possible to see about getting them provisioned a bit more heavily to see if it solves the problem?
17:37:33  <refack>joyee: could probably give stats about this
17:39:44  <refack>If it's mostly timeouts than it makes sense. But if it's a different fails, IMHO that makes those machines good canaries
17:48:33  <Trott>And here's one that seems to be Rackspace only so... https://github.com/nodejs/node/issues/22327
17:59:29  * sxaquit (Ping timeout: 246 seconds)