Smalltalk › Pharo › Pharo Smalltalk Developers

working moose build

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Tudor Girba-2

working moose build

Hi,

The Moose build including running tests now works based on the NBCog VM and the latest Pharo 2.0 (built on Ubuntu):
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/

There are 27 test failures.

I also tried on OS X using NBCog VM and the there is no crash. This scenario was also confirmed by Stephan although he reported more failures.

For reference, we are using the following script on Jenkins:

wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash
wget http://pharo.gforge.inria.fr/ci/image/PharoV20.sources
./vm.sh Pharo.image save $JOB_NAME
REPO=http://smalltalkhub.com/mc/Moose/Moose/main
./vm.sh $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development
./vm.sh $JOB_NAME.image moosetest --junit-xml-output
zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources

Cheers,
Doru

--
www.tudorgirba.com

"From an abstract enough point of view, any two things are similar."

Usman Bhatti

Re: working moose build

11 failures (-17)

https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/

:-)

Doru, if Mondrian tests are not really important, we can exclude it from the build report?

And may be include petit-parser tests in the report or we can create a different job for it?

usman

On Tue, Mar 12, 2013 at 10:29 PM, Tudor Girba <[hidden email]> wrote:

Hi,

The Moose build including running tests now works based on the NBCog VM and the latest Pharo 2.0 (built on Ubuntu):
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/

There are 27 test failures.

I also tried on OS X using NBCog VM and the there is no crash. This scenario was also confirmed by Stephan although he reported more failures.

For reference, we are using the following script on Jenkins:

wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash
wget http://pharo.gforge.inria.fr/ci/image/PharoV20.sources
./vm.sh Pharo.image save $JOB_NAME
REPO=http://smalltalkhub.com/mc/Moose/Moose/main
./vm.sh $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development
./vm.sh $JOB_NAME.image moosetest --junit-xml-output
zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources

Cheers,
Doru

--
www.tudorgirba.com

"From an abstract enough point of view, any two things are similar."

Tudor Girba-2

Re: working moose build

Hi,

The idea is to eliminate Mondrian altogether, but as long as it is part of Moose, its tests are important, so they will remain in the build.

But, in the meantime, I found the reason why the PetitSmalltalk tests were not ran, and I fixed the problem (we are now running 3350 tests and have 19 failures):
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/

The issue was that I only considered the packages that are mentioned in the configuration. However, the Monticello PetitSmalltalk package contains two sub-categories and this resulted in 3 RPackages (one for the root category, and two for the children), and thus, triggering the tests only from the root did not work.

Cheers,
Doru

On Mar 13, 2013, at 12:12 PM, Usman Bhatti <[hidden email]> wrote:

> 11 failures (-17)
> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/
>
> :-)
>
> Doru, if Mondrian tests are not really important, we can exclude it from the build report?
> And may be include petit-parser tests in the report or we can create a different job for it?
>
> usman
>
>
> On Tue, Mar 12, 2013 at 10:29 PM, Tudor Girba <[hidden email]> wrote:
> Hi,
>
> The Moose build including running tests now works based on the NBCog VM and the latest Pharo 2.0 (built on Ubuntu):
> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testReport/
>
> There are 27 test failures.
>
> I also tried on OS X using NBCog VM and the there is no crash. This scenario was also confirmed by Stephan although he reported more failures.
>
> For reference, we are using the following script on Jenkins:
>
> wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash
> wget http://pharo.gforge.inria.fr/ci/image/PharoV20.sources
> ./vm.sh Pharo.image save $JOB_NAME
> REPO=http://smalltalkhub.com/mc/Moose/Moose/main
> ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development
> ./vm.sh $JOB_NAME.image moosetest --junit-xml-output
> zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources
>
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "From an abstract enough point of view, any two things are similar."
>
>
>
>
>

--
www.tudorgirba.com

"Next time you see your life passing by, say 'hi' and get to know her."