00:15:00  * Fishrock123quit (Remote host closed the connection)
00:21:26  * jenkins-monitor1joined
00:21:30  * jenkins-monitorquit (Read error: Connection reset by peer)
00:23:51  * Fishrock123joined
01:02:33  * Fishrock123quit (Remote host closed the connection)
01:45:30  <jbergstroem>:(
02:02:55  * Fishrock123joined
02:07:35  * Fishrock123quit (Ping timeout: 258 seconds)
04:22:24  * node-ghjoined
04:22:24  * node-ghpart
04:23:12  * node-ghjoined
04:23:12  * node-ghpart
04:23:29  * node-ghjoined
04:23:29  * node-ghpart
05:04:33  * Fishrock123joined
05:09:20  * Fishrock123quit (Ping timeout: 260 seconds)
07:40:04  * evanlucas1joined
07:46:19  * evanlucasquit (Ping timeout: 260 seconds)
08:00:23  <rvagg>oi wut?
08:01:15  <rvagg>> Ping response time is too long or timed out.
08:01:41  <rvagg>network is fine, I'm on it right now and it's fine!
08:02:05  <rvagg>rebooting it for good measure
10:25:07  * mylesborinsquit (Quit: farewell for now)
10:25:38  * mylesborinsjoined
10:53:02  * evanlucas1changed nick to evanlucas
10:53:32  * evanlucaschanged nick to Guest94077
10:53:51  * Guest94077quit (Remote host closed the connection)
12:44:09  * evanlucasjoined
12:44:16  * evanlucasquit (Remote host closed the connection)
12:57:12  * evanlucasjoined
13:31:30  * node-ghjoined
13:31:30  * node-ghpart
13:31:49  <jbergstroem>rvagg: update slave.jar if you log into a box!
13:32:01  <jbergstroem>we want jnlp4 everywehre
13:36:43  * node-ghjoined
13:36:43  * node-ghpart
13:37:00  * node-ghjoined
13:37:00  * node-ghpart
14:31:25  * node-ghjoined
14:31:25  * node-ghpart
14:35:48  <evanlucas>is https://ci.nodejs.org/job/node-test-commit-linux/9404/nodes=ubuntu1204-clang341-64/ a known failure?
14:35:58  * Fishrock123joined
14:46:46  * node-ghjoined
14:46:46  * node-ghpart
15:23:56  * sgimenoquit (Remote host closed the connection)
16:02:09  <Trott>evanlucas: I have no idea, but since that's against v7.x-staging, I'd look to see if we added/dropped support for clang versions somewhere that might affect that specific host, especially given that clang is in the host's name and clang seems to be what failed in the build.
16:02:49  <Trott>mylesborins: Is this the source of your CITGM heartache or is something else going on as well? https://github.com/nodejs/citgm/issues/399
16:04:10  <Trott>Never mind, I see that you address it in https://github.com/nodejs/citgm/pull/400.
16:13:23  <mylesborins>Trott yeah so about that
16:13:41  <mylesborins>the weird thing with the citgm stuff is it just started happening in the last two weeks or so
16:15:19  <Trott>So either something changed on CI or something changed with ESLint or something changed with CITGM, and you're pretty sure it's not that last one?
16:32:39  * node-ghjoined
16:32:39  * node-ghpart
16:33:37  <mylesborins>nothing changed in CI or with CITGM afaik
16:33:42  <mylesborins>there was a release of eslint recently
16:33:46  <mylesborins>I'm trying to create a repro
16:46:47  * node-ghjoined
16:46:48  * node-ghpart
17:00:20  <mylesborins>Trott so it looks like the project that are failing do not have an eslint config
17:00:32  <mylesborins>I think I may have figured out the issue
17:00:32  <mylesborins>:D
17:00:35  <mylesborins>gimme a momo
17:01:32  * Fishrock123quit (Remote host closed the connection)
17:10:34  <Trott>One momo granted.
17:10:35  * Fishrock123joined
17:24:05  <jbergstroem>the only problems i know of re clang is that we updated gcc to 4.9 on the same machine(s)
17:24:31  <jbergstroem>it was requested that it should be updated since we didn't support the version of gcc any longer
17:30:33  * chorrelljoined
18:37:28  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:06:07  * Fishrock123quit (Remote host closed the connection)
19:08:37  * Fishrock123joined
19:14:51  * Fishrock123quit (Remote host closed the connection)
19:15:34  * Fishrock123joined
19:15:41  * Fishrock123quit (Remote host closed the connection)
19:41:13  * chorrelljoined
19:51:36  * node-ghjoined
19:51:42  * node-ghpart
20:20:08  * Fishrock123joined
20:23:42  * Fishrock123quit (Read error: Connection reset by peer)
20:23:44  * Fishrockjoined
20:25:21  * jenkins-monitor1quit (Remote host closed the connection)
20:25:32  * jenkins-monitorjoined
20:26:56  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:54:28  * chorrelljoined
21:03:30  * Fishrockquit (Remote host closed the connection)
21:03:37  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
21:04:10  * Fishrock123joined
21:04:17  * Fishrock123quit (Remote host closed the connection)
21:34:08  <Trott>I don't think there's any options in the stress test that run the test on win2008r2 + vs2015. I'm trying to replicate/fix https://ci.nodejs.org/job/node-test-binary-windows/7965/RUN_SUBSET=2,VS_VERSION=vs2015,label=win2008r2/console and other combinations don't seem to exhibit the problem. Any chance we can get that combination added to the drop-down? /cc
21:34:08  <Trott>joaocgreis
21:35:09  * Fishrock123joined
22:06:20  * Fishrock123quit (Ping timeout: 252 seconds)
22:48:13  <joaocgreis>Trott: here now, let me take a look
23:11:19  * Fishrock123joined
23:31:34  * Fishrock123quit (Remote host closed the connection)
23:35:26  * Fishrock123joined
23:41:00  * Fishrock123quit (Remote host closed the connection)
23:55:35  * Fishrock123joined
23:56:17  * Fishrock123quit (Client Quit)