moose build - pharo vm crash

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 list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

Done.

Thanks for looking into it,

Doru

On Tue, Aug 6, 2013 at 4:46 PM, Nicolas Anquetil <[hidden email]> 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 list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

cool :)

now we need to finish fixing the vm and release it :D

Esteban

On Aug 6, 2013, at 5:29 PM, Nicolas Anquetil <[hidden email]> wrote:

and worked.

the build is yellow now because of the test I created for issue 960

nicolas

On 08/06/2013 04:49 PM, Tudor Girba wrote:

Done.

Thanks for looking into it,

Doru

On Tue, Aug 6, 2013 at 4:46 PM, Nicolas Anquetil <[hidden email]> 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 list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

thanks a lot Esteban

nicolas

On 08/06/2013 05:36 PM, Esteban Lorenzano wrote:

cool :)

now we need to finish fixing the vm and release it :D

Esteban

On Aug 6, 2013, at 5:29 PM, Nicolas Anquetil <[hidden email]> wrote:

and worked.

the build is yellow now because of the test I created for issue 960

nicolas

On 08/06/2013 04:49 PM, Tudor Girba wrote:

Done.

Thanks for looking into it,

Doru

On Tue, Aug 6, 2013 at 4:46 PM, Nicolas Anquetil <[hidden email]> 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 list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- 
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev