Investigate flaky test-vm-timeout.js

[Trott]

• Version: master
• Platform: CentOS 5 64-bit
• Subsystem: test vm

Example failure: https://ci.nodejs.org/job/node-test-commit-linux/3362/nodes=centos5-64/tapTestReport/test.tap-1025/

not ok 1025 test-vm-timeout.js
# FATAL ERROR: v8::FromJust Maybe value is Nothing.

[mscdex]

This same test recently failed on Windows, but with a different error:

not ok 267 parallel/test-vm-timeout
# vm.js:35
#     return realRunInContext.call(this, contextifiedSandbox, options);
#                             ^
# Error: Script execution interrupted.
#     at Error (native)
#     at ContextifyScript.Script.runInContext (vm.js:35:29)
#     at ContextifyScript.Script.runInNewContext (vm.js:41:15)
#     at Object.exports.runInNewContext (vm.js:72:17)
#     at context.runInVM (C:\workspace\node-test-binary-windows\RUN_SUBSET\3\VS_VERSION\vcbt2015\label\win10\test\parallel\test-vm-timeout.js:29:10)
#     at evalmachine.<anonymous>:1:1
#     at ContextifyScript.Script.runInContext (vm.js:35:29)
#     at ContextifyScript.Script.runInNewContext (vm.js:41:15)
#     at Object.exports.runInNewContext (vm.js:72:17)
#     at C:\workspace\node-test-binary-windows\RUN_SUBSET\3\VS_VERSION\vcbt2015\label\win10\test\parallel\test-vm-timeout.js:32:6

[addaleax]

That error message is due to #6635, but it doesn’t seem to make sense that it fails in this particular way in test-vm-timeout.js. I’m trying to reproduce this locally, but no success on Linux (x64 Ubuntu 16.04) so far.

[Trott]

This one has gotten relentless on Windows recently. /cc @nodejs/platform-windows @nodejs/testing