Good news everyone (c) :) Currently i am the only happily owner of JIT VM , which no longer crashing while running all Pharo tests... I will prepare new configs and publish them soon. P.S. @Henrik Your MethodContextTest>>testClosureRestart are failing. P.P.S. @Lukas , i made small modifications to your HudsonBuildTools, see an attached changeset. First i introducing a counter, which allows to arrange files in order they run (it is important to know which tests are run before, because it could be possible that crash were caused by combination of tests), and also added stream flushing before running each test case, so if VM will crash, we will observe a half-populated file. So, on Hudson, instead of running: HDTestReport runCategories: Smalltalk organization categories one should run : HDTestReport resetCounter. HDTestReport runCategories: Smalltalk organization categories Please let me know if you willing to integrate this changeset. Maybe in separate subclass, but we should be prepared that tests could crash VM (because we will be testing newly built VMs), so it is important to know which test were causing failure. P.P.S. On second thought, i thinking that it could be made even more direct by overwriting a 'runningCase.txt' file each time we running test.. P.P.P.S. It would be nice to integrate stdout output into images and make stdout == Transcript in headless mode, so running any image in headless mode by default will print stuff on stdout, so we don't need to worry about flushing files etc and can easily see progress via Hudson console output view. -- Best regards, Igor Stasenko AKA sig.