How are you loading Seaside? I thought the point of declaring versions in Metacello configurations was so that at some point in the future you could create de novo an image identical to one you created in the past. Why not just pick a Seaside version and load it every time? e.g. (ConfigurationOfSeaside30 project version:'3.0.8') load. Camillo Bruni-3 wrote
I am still struggling with the VM acceptance test. Currently we're loading Seaside and Moose, two very big projects which hopefully stress many parts of the VM.
The problem is, that these two projects evolve by themselves, adding another axis of freedom which I would like to avoid.
So is there an easy way to freeze a configuration and store it on our fileserver, so that we have a fixed reference? (Note, we use a 2.0 image)
If we have that, I can even integrate the validation process into the travis build which should make contributions to the pharo-vm much easier...
signature.asc (457 bytes) <http://forum.world.st/attachment/4716692/0/signature.asc>;
-- View this message in context: http://forum.world.st/VM-acceptance-tests-tp4716692p4716702.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.