Done.
Thanks for looking into it,
Doru
On Tue, Aug 6, 2013 at 4:46 PM, Nicolas Anquetil
<Nicolas.Anquetil(a)inria.fr>wrote;wrote:
We were looking at that with the local gurus.
first thing they suggested was to try with the lastest VM.
Can you change the job?
nicolas
On 08/06/2013 04:43 PM, Tudor Girba wrote:
Hi,
It seems that the Moose build crashes the VM since yesterday evening due
to a failing test. The image is based on Pharo 2.0 and is running a stable
VM on Ubuntu.
See some details here:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/804/console
The script to reproduce the problem (on Ubuntu) is:
#-------------------
wget --quiet -O -
http://get.pharo.org/20+vm | bash
./pharo Pharo.image save $JOB_NAME
REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
./pharo $JOB_NAME.image config $REPO ConfigurationOfMoose
--install=development
./pharo $JOB_NAME.image mooseimagesetup
./pharo $JOB_NAME.image moosetest --junit-xml-output
mv ./pharo-vm/PharoV20.sources ./
zip $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources
#-------------------
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Nicolas Anquetil -- RMod research team (Inria)
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev