I just added http://files.pharo.org/image/20/vm-test.zip which is used to test the new VM builds This way we don't have 2 changing variables for the VM builds, the image stays fixed and only the VM behind changes. We can add a future job that tests the VM against the current image, but I think that will be of lesser importance as we cannot directly see if the VM performs well or not if there are already failing tests in the latest image. vm-test.zip changes compared to the latest 2.0 image ---------------------------------------------------- - fixed version with manual updates - all red tests are removed - all unstable tests are removed TODO: ----- - maybe add some more VM stress tests (adding classes / recompiling classes / adding instvars)