00:08:41  * dbeveniusjoined
00:13:15  * dbeveniusquit (Ping timeout: 246 seconds)
00:28:40  * dbeveniusjoined
00:32:58  * dbeveniusquit (Ping timeout: 246 seconds)
00:52:08  * dbeveniusjoined
00:55:23  <joaocgreis>https://ci.nodejs.org/computer/test-scaleway-ubuntu1604-armv7l-1/ back online
00:56:34  * dbeveniusquit (Ping timeout: 250 seconds)
01:06:58  <rvagg>joaocgreis: hm, I only recently had to bring that one back online with a forced restart, perhaps we're having hardware problems.. let's remember to monitor and if it happens again to this machine we should think about alternative solutions.
01:08:37  * dbeveniusjoined
01:13:08  * dbeveniusquit (Ping timeout: 244 seconds)
02:08:41  * dbeveniusjoined
02:13:17  * dbeveniusquit (Ping timeout: 246 seconds)
02:29:22  * dbeveniusjoined
02:34:04  * dbeveniusquit (Ping timeout: 246 seconds)
02:48:44  * dbeveniusjoined
02:53:15  * dbeveniusquit (Ping timeout: 255 seconds)
03:08:26  * dbeveniusjoined
03:12:47  * dbeveniusquit (Ping timeout: 246 seconds)
03:22:54  * dbeveniusjoined
05:00:05  * dbeveniusquit (Remote host closed the connection)
05:08:49  * dbeveniusjoined
05:12:04  * dbeveniusquit (Remote host closed the connection)
05:12:10  <Trott>Something happened with the most recent coverage run such that sorting no longer works in the output. Results from two nights ago (https://coverage.nodejs.org/coverage-1e7823dd4ec1e0d0/index.html) is sortable by column (click on one). Most recent (https://coverage.nodejs.org/coverage-09cdc3782488d2e6/index.html) is not and a relevant-seeming error shows up in the console. Anyone know if anything changed recently with the
05:12:10  <Trott>coverage job?
05:12:16  * dbeveniusjoined
06:54:57  <richardlau>Trott: https://coverage.nodejs.org/coverage-09cdc3782488d2e6/sorter.js and https://coverage.nodejs.org/coverage-1e7823dd4ec1e0d0/sorter.js are different. I think it's https://github.com/istanbuljs/istanbuljs/pull/289 -- I'm guessing a new module was published (we ignore C8's package-lock.json when installing in our Makefile).
07:35:17  <richardlau>Raised https://github.com/istanbuljs/istanbuljs/pull/369
09:37:54  * sxa_joined
09:38:13  * sxajoined
13:49:10  <Trott>Thanks!
13:50:13  <Trott>Is https://ci.nodejs.org/job/node-test-binary-windows-2/203/COMPILED_BY=vs2017,RUNNER=win2008r2-vs2017,RUN_SUBSET=0/testReport/(root)/test/parallel_test_child_process_fork_exec_path/ a problem with the test or a problem with the host? refack
13:52:26  <refack>it's a problem with the test. Seems like `.tmp.2\node-copy.exe` is still running, but it might be left over from a previous test, and hit here because it calls `tempdir.refresh()`
14:34:41  <Trott>Two different node executables in `parallel` should not be able to share the same `.tmp` directory. At least in theory....
14:36:23  <refack>I've been running that test locally, and it's actually a leftover of the same test file.
14:36:37  <refack>is too tight https://www.irccloud.com/pastebin/SFQRsdBs/test.js
14:37:43  <Trott>Yeah, so either Windows child exits before it actually, you know, exits...Or something else, but the cleanup is unnecessary. At a minimum, it should probably be wrapped in a try/catch. Maybe removed entirely. Depends on how big the leftover file will be.
14:40:02  <refack>It's a node binary, ~20MB
14:41:06  <Trott>Test usually passes but just fails once in a while for you locally?
14:42:19  <refack>It doesn't fail on Windows 10, but does on 2008R2. It's a speed thing. The OS keeps the handle open just a tad bit longer
14:43:11  <Trott>I guess the question is: Is that a bug? (I would say it is. But there also might not be a whole lot we can do about it?)
14:43:38  <refack>2008R2 goes EOL on 2019-12-31
14:44:03  <refack>It's one of those things that `gracefull-fs` was made for
14:44:48  <refack>https://github.com/libuv/libuv/pull/2122
14:46:59  <Trott>Well, if it's only failing very rarely and we won't need to worry about it after December, I guess I'm OK with ignoring it for now.... How are you feeling about it?
14:47:32  <refack>https://ci.nodejs.org/job/node-stress-single-test/2201/nodes=win2008r2-vs2017/console
14:47:46  * dbeveniusquit (Remote host closed the connection)
14:48:30  <refack>strong enough to try and mask it https://github.com/nodejs/node/pull/27277
15:33:03  * dbeveniusjoined
15:47:45  <refack>Meanwhile I found that `test/parallel/test-child-process-exec-timeout.js` is leaving a Zombie process behind...
16:33:43  * dbeveniusquit (Remote host closed the connection)
16:41:14  * dbeveniusjoined
16:46:12  * dbeveniusquit (Ping timeout: 255 seconds)
17:00:10  * dbeveniusjoined
17:04:31  * dbeveniusquit (Ping timeout: 246 seconds)
17:20:17  * dbeveniusjoined
17:24:38  * dbeveniusquit (Ping timeout: 245 seconds)
17:40:16  * dbeveniusjoined
17:44:39  * dbeveniusquit (Ping timeout: 246 seconds)
17:58:48  * sxa_quit (Ping timeout: 245 seconds)
17:58:48  * sxaquit (Ping timeout: 250 seconds)
18:02:21  * dbeveniusjoined
18:06:36  * dbeveniusquit (Ping timeout: 250 seconds)
18:07:01  * dbeveniusjoined
20:06:59  * dbeveniusquit (Remote host closed the connection)
20:19:19  * dbeveniusjoined
20:23:40  * dbeveniusquit (Ping timeout: 246 seconds)
20:39:25  * dbeveniusjoined
20:43:51  * dbeveniusquit (Ping timeout: 246 seconds)
20:53:30  * dbeveniusjoined
20:58:20  * dbeveniusquit (Ping timeout: 268 seconds)
22:24:52  * kriskropdquit (Ping timeout: 252 seconds)
23:32:35  * dbeveniusjoined
23:36:45  * dbeveniusquit (Ping timeout: 246 seconds)
23:53:31  * dbeveniusjoined
23:58:02  * dbeveniusquit (Ping timeout: 250 seconds)