00:13:57  * Fishrock123quit (Remote host closed the connection)
01:11:09  * Fishrock123joined
01:11:46  * Fishrock123quit (Remote host closed the connection)
04:05:18  * apapirovskijoined
04:32:47  * apapirovskiquit (Remote host closed the connection)
04:42:01  <Trott>Build failures across all Windows hosts. joaocgreis
04:42:35  <Trott>Sample: https://ci.nodejs.org/job/node-test-binary-windows/13680/COMPILED_BY=vs2017,RUNNER=win10,RUN_SUBSET=0/console
04:42:52  <Trott>https://www.irccloud.com/pastebin/7OWdjUCc/
04:43:27  * apapirovskijoined
05:01:17  * apapirovskiquit (Remote host closed the connection)
05:43:28  <joaocgreis>Trott: that one is the CI working as expected, it's a problem with the PR. Apparently the author is already working on it.
05:55:02  * Fishrock123joined
05:56:28  * sgimenoquit (Ping timeout: 240 seconds)
05:56:42  * Fishrock123quit (Client Quit)
05:56:50  * sgimenojoined
09:40:57  * seishunjoined
11:16:56  <rvagg>still down 2 Rackspace release machines, trying to resolve that somehow still, just nobody do a release this week eh?
11:18:12  <rvagg>might only be for older branches tho, v4 maybe
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
12:38:16  * apapirovskijoined
12:49:58  * apapirovskiquit (Quit: Leaving...)
12:56:32  <rvagg>mhdawson, joaocgreis: FYI I've provisioned a new release-rackspace-win2008r2-x64-2 to replace the one that's "on hold" @ Rackspace. I took an image of the root disk and started up a new server on it.
12:56:39  <rvagg>mhdawson, joaocgreis: IP address and credentials are in secrets/build/release/windows-servers.md, it's working through the small backlog of x64 & x86 (I assume). Will remove the old one once we can & will assess what to do with the other one later, perhaps we'll just get it back as normal.
18:59:06  * apapirovskijoined
22:32:43  * apapirovskiquit (Remote host closed the connection)
22:49:23  * seishunquit (Ping timeout: 265 seconds)
22:54:28  * apapirovskijoined