It is the cause of most of the failures on https://ci.nodejs.org/job/node-test-binary-windows-2/: - https://ci.nodejs.org/job/node-test-binary-windows-2/1274/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1272/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1270/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1268/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1267/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1288/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1285/ - https://ci.nodejs.org/job/node-test-binary-windows-2/1284/ etc... @nodejs/platform-windows @nodejs/workers @Trott I guess I should PR to mark this test as flaky? <!-- Thank you for reporting a possible bug in Node.js. Please fill in as much of the template below as you can. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify the affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you can. --> * **Version**: master * **Platform**: Windows * **Subsystem**: workers <!-- Please provide more details below this comment. -->
It is the cause of most of the failures on https://ci.nodejs.org/job/node-test-binary-windows-2/:
etc...
@nodejs/platform-windows @nodejs/workers @Trott I guess I should PR to mark this test as flaky?