not really true... the old vm should appear just in really old vm builds (there was a bug last week introduced in the last moment that was showing again the warning, but that is fixed now).now... I would really like you to stay using the new vms, and report the crashes so we can work on them... we cannot blindly fix, you now :)
EstebanOn 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,DoruOn 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:
1. download and unzip the latest Moose 4.8:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/artifact/Moose-latest-dev-4.8.zip
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
--"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev