Hi,
Doru, I just compiled a new version of the VM, that mixes a merge from latest Eliot sources with a lot of work in the optimization flags to prevent random crashes (yes, I hate C and its nondeterministic behavior for VMs :P). Moose tests are now not crashing in my machine (both in mac and unix... didn't tested in windows).
Can you check if this solves the problem?
https://ci.inria.fr/pharo/view/VM/job/PharoVM/Architecture=32,Slave=vm-build... https://ci.inria.fr/pharo/view/VM/job/PharoVM/Architecture=32,Slave=vm-build...
cheers, Esteban
On Mar 12, 2013, at 9:22 AM, Tudor Girba tudor@tudorgirba.com wrote:
It would be good to have a parallel job, but the problem is that you will get a message saying that the VM is too old for the Pharo 2.0 image.
Cheers, Doru
On Tue, Mar 12, 2013 at 9:05 AM, Usman Bhatti usman.bhatti@gmail.com wrote: Doru,
In the meantime, can we revert to CogVM because currently we cannot see the status of fixes and we cannot go any further with Moose 4.8 or may be create parallel jobs on Cog and Pharo vms ?
On Mon, Mar 11, 2013 at 9:53 PM, Tudor Girba tudor@tudorgirba.com wrote: Hi,
Where should I report Pharo VM crashes with Pharo 2.0?
In particular, I wanted to report the problem related to running Moose tests from the command line:
You can reproduce it on Mac, quite consistently: just run the attached script (you need to have wget installed), or do it manually:
- download and unzip the latest Moose 4.8:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/artif... 2. download and unzip the latest Pharo VM: http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip 3. execute: ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest
The VM crashes, but there is no trace of the error.
Cheers, Doru
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"