00:43:49  * dbeveniusjoined
00:47:57  * dbeveniusquit (Ping timeout: 246 seconds)
01:03:24  * dbeveniusjoined
01:07:33  * dbeveniusquit (Ping timeout: 246 seconds)
01:51:09  * dbeveniusjoined
01:55:16  * dbeveniusquit (Ping timeout: 246 seconds)
03:09:35  * dbeveniusjoined
03:13:59  * dbeveniusquit (Ping timeout: 255 seconds)
03:29:28  * dbeveniusjoined
03:33:47  * dbeveniusquit (Ping timeout: 245 seconds)
04:10:09  * dbeveniusjoined
04:14:27  * dbeveniusquit (Ping timeout: 246 seconds)
04:16:05  * dbeveniusjoined
05:17:08  * node-slack-botpart
05:17:20  * node-slack-botjoined
05:19:32  * dbeveniusquit (Ping timeout: 255 seconds)
05:30:36  * sxajoined
05:32:06  * dbeveniusjoined
06:41:50  <Trott>refack: I saw https://ci.nodejs.org/job/node-test-commit-windows-fanned/24927/ and guessed that you're bisecting on master to find the bad commit, so I kicked off https://ci.nodejs.org/job/node-test-commit-windows-fanned/24932/ which is testing 3d4db3a7bf16a788e59ab76ca8c4a37069b59e80...
07:06:59  * dbeveniusquit (Remote host closed the connection)
07:10:48  * dbeveniusjoined
07:15:27  * dbeveniusquit (Ping timeout: 245 seconds)
07:29:33  <Trott>https://ci.nodejs.org/job/node-test-commit-windows-fanned/24933/ is testing eb9e6c015705847190147201c587e1e668358a78.
07:40:36  * sxaquit (Excess Flood)
07:40:56  * sxajoined
07:45:53  * sxaquit (Ping timeout: 245 seconds)
08:00:53  * sxajoined
08:10:14  * dbeveniusjoined
08:14:37  * sxaquit (Ping timeout: 245 seconds)
08:35:26  * sxajoined
09:02:07  * sxaquit (Ping timeout: 245 seconds)
09:35:09  * sxajoined
09:35:09  * dbeveniusquit (Remote host closed the connection)
09:41:00  * sxaquit (Ping timeout: 246 seconds)
09:52:29  * dbeveniusjoined
09:56:45  * dbeveniusquit (Ping timeout: 246 seconds)
10:09:46  * dbeveniusjoined
10:14:40  * dbeveniusquit (Ping timeout: 272 seconds)
10:48:50  * dbeveniusjoined
10:53:18  * dbeveniusquit (Ping timeout: 250 seconds)
11:13:48  * dbeveniusjoined
11:17:57  * dbeveniusquit (Ping timeout: 245 seconds)
11:20:00  * sxajoined
11:27:11  * sxaquit (Ping timeout: 255 seconds)
11:49:49  * dbeveniusjoined
11:54:32  * dbeveniusquit (Ping timeout: 268 seconds)
11:55:21  * srl295quit (Quit: Connection closed for inactivity)
12:22:09  * dbeveniusjoined
12:26:32  * dbeveniusquit (Ping timeout: 246 seconds)
12:37:58  * dbeveniusjoined
12:42:38  * dbeveniusquit (Ping timeout: 268 seconds)
13:26:52  * lucalanzianiquit (Ping timeout: 244 seconds)
13:28:50  * dbeveniusjoined
13:33:11  * dbeveniusquit (Ping timeout: 255 seconds)
13:38:50  * dbeveniusjoined
13:46:06  <refack>AFAICT it's d1011f6bbfadfa254925014896aa710f02403770
13:46:55  <refack>But only in combination with the being rebased on master
14:11:18  * dbeveniusquit (Ping timeout: 244 seconds)
14:29:00  * dbeveniusjoined
14:33:23  * dbeveniusquit (Ping timeout: 245 seconds)
15:20:42  <Trott>That's the last commit I'm bisecting.... https://ci.nodejs.org/job/node-test-commit-windows-fanned/24944/
15:21:01  <Trott>And here's a re-run of that PR's CI just because: https://ci.nodejs.org/job/node-test-pull-request/20981/
15:22:10  <refack>d1011f6 is 26196
15:23:17  <Trott>Pasted the wrong link, sorry: https://ci.nodejs.org/job/node-test-pull-request/20982/
15:24:09  <Trott>Also, we seem to have a SmartOS infra problem with test-joyent-smartos16-x64-1. https://ci.nodejs.org/computer/test-joyent-smartos16-x64-1/builds
15:24:25  <refack>SmartOS should be fixed
15:24:45  <refack>https://ci.nodejs.org/job/node-test-commit-smartos/nodes=smartos16-64/
15:24:47  <Trott>Ah, OK. Just had to remove .git and let it rebuild it the next time?
15:25:23  <refack>Yeah. IT's https://github.com/nodejs/build/issues/1682
15:25:28  <Trott>k thx
15:26:12  <Trott>Is the a clear next step about d1011f6/Windows?
15:26:20  <Trott>*Is there a
15:27:27  <refack>Need to refactor the code a bit. Use a more predicable way to run the singletons' ctors
15:27:47  <refack>I'll try to get that done today
15:28:57  * refackhaving fun reading last night's logs in this beautiful Saturday morning
15:29:13  <refack>I wonder how much of history was created this way
15:29:16  <refack>https://usercontent.irccloud-cdn.com/file/bz0ACTfj/image.png
15:30:50  * lucalanzianijoined
15:37:39  <refack>this is strange... if you run a `test-pull-request` on a landed PR with rebase on `<pr base branch>` you're actually testing master
15:37:43  <refack>https://www.irccloud.com/pastebin/hWoxQIDU/
15:39:45  <refack>but the binary created by https://ci.nodejs.org/job/node-compile-windows/24622/label=win-vs2017-x86/ seems Ok
15:39:56  <Trott>I guess that makes sense since the rebasing the PR is effectively a no-op?
15:39:57  <refack>Strike that. It's wonky
15:40:23  <Trott>👍
15:40:46  <refack>Too many serial numbers for this time of day
16:29:02  * dbeveniusjoined
16:33:28  * dbeveniusquit (Ping timeout: 250 seconds)
16:48:45  * dbeveniusjoined
16:53:26  * dbeveniusquit (Ping timeout: 255 seconds)
17:07:49  * dbeveniusjoined
17:12:28  * dbeveniusquit (Ping timeout: 250 seconds)
17:29:41  * sxajoined
17:30:05  * dbeveniusjoined
17:34:23  * dbeveniusquit (Ping timeout: 255 seconds)
17:34:34  * BridgeAR2changed nick to BridgeAR
17:49:08  * dbeveniusjoined
17:53:22  * dbeveniusquit (Ping timeout: 245 seconds)
19:28:55  * dbeveniusjoined
19:33:33  * dbeveniusquit (Ping timeout: 246 seconds)
21:39:39  * dbeveniusjoined
22:13:41  * dbeveniusquit (Ping timeout: 268 seconds)
22:29:15  * dbeveniusjoined
22:33:38  * dbeveniusquit (Ping timeout: 255 seconds)
22:49:17  * dbeveniusjoined
22:54:02  * dbeveniusquit (Ping timeout: 272 seconds)