Known Issues

Running tests under Windows 7 (possibly XP too)

When executing the tests using the command line tool on windows, you can occasionally receive the following fatal error:

Fatal error in gc: Bad stack base in GC_register_my_thread_inner

This appears to be an issue with a third party library NekoVM is using and is unfortunately beyond our control.

Further information:

• http://haxe.1354130.n2.nabble.com/neko-fatal-error-in-gc-td4272564.html
• http://haxe.1354130.n2.nabble.com/Bad-stack-base-in-GC-register-my-thread-inner-td5623216.html

haxelib run munit fails to exit with correct error code on OSX

There is a bug in haxelib on osx that prevents exit codes > 0 from being returned by the haxelib process.

See http://code.google.com/p/haxe/issues/detail?id=879 for more details

Running swf and js tests in Safari

There is currently a bug which prevents tests being run in the Safari browser for js, swf and swf9 platforms. The bug seems to relate to the nekotools server injecting header information into the body of html and js files.

HTTP POST causes Nekotools server to hang (fixed in 2.1.2)

There were 2 main issues causing munit to hang:

• when too many errors were being printed by the compiler,
• when reaching a number of tests and using the JUnit report client.

Those issues have been fixed in release 2.1.2.