01:14:31  * node-ghjoined
01:14:31  * node-ghpart
02:09:09  * nginxquit (Ping timeout: 260 seconds)
03:42:09  * nginxjoined
03:44:42  * nginxquit (Client Quit)
05:31:04  * srl295quit (Quit: Connection closed for inactivity)
06:36:27  * seishunjoined
07:43:57  * seishunquit (Ping timeout: 240 seconds)
10:25:21  * mylesborinsquit (Quit: farewell for now)
10:25:29  * mylesborinsjoined
11:27:32  * sxajoined
13:47:53  * node-ghjoined
13:47:53  * node-ghpart
13:51:35  * node-ghjoined
13:51:35  * node-ghpart
14:15:11  * node-ghjoined
14:15:11  * node-ghpart
15:05:32  * node-ghjoined
15:05:32  * node-ghpart
15:11:34  * node-ghjoined
15:11:34  * node-ghpart
15:35:21  * node-ghjoined
15:35:21  * node-ghpart
15:41:29  * node-ghjoined
15:41:29  * node-ghpart
15:54:23  * node-ghjoined
15:54:24  * node-ghpart
16:19:41  * node-ghjoined
16:19:41  * node-ghpart
16:57:47  * seishunjoined
17:14:33  * node-ghjoined
17:14:33  * node-ghpart
17:37:27  * sxaquit (Ping timeout: 240 seconds)
19:00:59  * node-ghjoined
19:00:59  * node-ghpart
19:22:24  * node-ghjoined
19:22:24  * node-ghpart
19:23:01  * node-ghjoined
19:23:01  * node-ghpart
19:55:38  * node-ghjoined
19:55:38  * node-ghpart
20:33:57  * seishunquit (Ping timeout: 240 seconds)
21:10:15  * node-ghjoined
21:10:15  * node-ghpart
21:21:55  * seishunjoined
21:37:10  * seishunquit (Read error: Connection reset by peer)
21:46:52  * node-ghjoined
21:46:52  * node-ghpart
22:01:18  <mmarchini_>So we test nodegyp on 0.10 but not on 10? Thatโ€™s pretty dreadful and worrying
22:01:54  <mmarchini_>๐Ÿ˜•
22:02:32  <refack>Don't bring your makes-perfect-sense logic here...
22:02:49  <refack>P.S. how's NodeSummit?
22:03:55  <mmarchini_>Pretty fun so far ๐Ÿ˜ƒ
22:04:02  <refack>Ohh and we have a bunch of native and napi addons as part of the core test suite, so we get some coverage for node-gyp anyway (just not CI for actual development... and I'm on that)
22:38:25  <richardlau>We do test node-gyp on 10: https://ci.nodejs.org/job/nodegyp-test-pull-request/65/
22:38:35  <richardlau>I think it depends which branch of node-gyp is tested
22:38:56  <richardlau>i.e. node-gyp v3.x still tests against v0.10 and v0.12 (!)
22:40:16  <refack>We just skip v0.10 & v0.12 if it's node-gyp@4.x.x. But we don't test against nightlies (i.e. v11)
22:41:28  <richardlau>Right, but the addon tests in Node.js do test that the node-gyp in npm still works. (kind of, they don't test the headers tarball works).
22:43:38  <TimothyGu>https://ci.nodejs.org/job/node-test-binary-windows/18732/COMPILED_BY=vs2017,RUNNER=win10,RUN_SUBSET=0/console
22:43:46  <TimothyGu>error: pathspec 'refs/remotes/jenkins_tmp/jenkins-node-test-commit-windows-fanned-19456-bin-win-vs2017' did not match any file(s) known to git.
22:43:50  <TimothyGu>I assume this isn't intentional
22:44:20  <refack>Can't resume a failed windows build, sorry
22:46:46  <TimothyGu>Ah heh
22:47:07  <TimothyGu>Let me try restarting it
22:47:17  <mmarchini_>Oh, I must've misunderstood the job configs
23:06:08  * node-ghjoined
23:06:08  * node-ghpart