Several tests fail on Windows due to a node.js bug.

[juj]

After the commit 14544cf , several tests began to fail on Windows: http://clb.demon.fi:8112/builders/win-incoming/builds/257/steps/Tests-other/logs/stdio

The affected tests:

other.test_no_exit_runtime
other.test_warn_undefined
other.test_unaligned_memory
other.test_stat_silly
other.test_simd
other.test_prepre
other.test_multidynamic_link
other.test_mdkir_silly
other.test_link_memcpy
other.test_init_file_at_offset
other.test_global_inits
other.test_emversion
other.test_embed_file_dup
other.test_dup_o_in_a
other.test_demangle

The cause of the failure was reduced to a Python bug, which I reported here: http://bugs.python.org/issue22066

As a workaround, reverting the line process.exit(status); back to throw new ExitStatus(status); lets the tests pass. I'm looking for a better workaround now.

[juj]

Further testing makes it look like that this is not actually an issue in python, but a node.js issue nodejs/node-v0.x-archive#1669 , which I see @kripken has commented on before as well.

[juj]

The underlying issue is now reported fresh at nodejs/node-v0.x-archive#8329 , since it still occurs and the previous reports of this in node.js repo have either been closed or are a bit different.