00:05:58  <maclover7>addaleax: https://transfer.sh/npRiq/outjm.txt
00:06:42  <addaleax>maclover7: is that local or from the benchmarking machine?
00:06:56  <maclover7>addaleax: from the machine
00:07:09  <addaleax>maclover7: ah, nice!
00:07:24  <maclover7>it's a few days old already, but still something
00:07:50  <addaleax>yea, the PR hasn’t changed in any significant way
00:27:39  * BridgeAR1joined
00:31:09  * BridgeARquit (Ping timeout: 260 seconds)
01:58:48  * BridgeAR1quit (Ping timeout: 246 seconds)
06:41:00  * sgimenoquit (Ping timeout: 256 seconds)
06:53:20  * sgimenojoined
07:17:45  * srl295quit (Quit: Connection closed for inactivity)
09:26:15  * seishunjoined
10:25:10  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
10:27:27  * seishunquit (Ping timeout: 240 seconds)
10:36:48  * seishunjoined
11:31:42  * node-ghjoined
11:31:42  * node-ghpart
12:01:33  * node-ghjoined
12:01:33  * node-ghpart
12:24:41  * evanlucasjoined
18:15:47  * chorrelljoined
18:34:13  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:45:16  * node-ghjoined
18:45:16  * node-ghpart
19:08:38  * node-ghjoined
19:08:38  * node-ghpart
19:30:13  * seishunquit (Disconnected by services)
19:30:20  * seishunjoined
19:36:21  * tnnneljoined
19:38:22  * tnnnelquit (Remote host closed the connection)
20:03:44  * BridgeAR1joined
20:33:24  * BridgeAR1quit (Ping timeout: 260 seconds)
20:50:10  * seishunquit (Ping timeout: 264 seconds)
20:51:06  * lanceballchanged nick to lance|afk
21:23:10  * seishunjoined
21:30:25  * mylesborinsquit (Excess Flood)
21:30:46  * mylesborinsjoined
21:43:24  <addaleax>could somebody make sure the tmpdir for one of the windows machines is okay/remove it? https://ci.nodejs.org/job/node-test-binary-windows/15685/
21:45:18  * seishunquit (Ping timeout: 246 seconds)
22:04:04  <Trott>joaocgreis refack ^^^^^^^
23:17:17  <joaocgreis>that's a new one, let me see what I can find about it
23:27:23  <joaocgreis>addaleax: I see that happened on two runs, testing the same PR. It is possible that some test that run before the ones that failed left behind a node executable running, does that make any sense? I remember we had to change some tests some time ago to call taskkill for child processes
23:44:51  <addaleax>joaocgreis: yes, it’s quite possible that there are pending processes (not necessarily node processes) sticking around