roassal2 job sets the author
Locked
 
|
The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests.
Here is the new script: ---- wget --quiet -O - http://get.pharo.org/30+vm | bash
./pharo Pharo.image save $JOB_NAME ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development
./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*"
mv ./pharo-vm/PharoV20.sources ./ zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources ---- Cheers, Doru "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Thanks!
This is great! Native Boost does something that requires the author name Alexandre On Jan 28, 2014, at 7:09 AM, Tudor Girba <[hidden email]> wrote: > The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests. > > > Here is the new script: > > ---- > wget --quiet -O - http://get.pharo.org/30+vm | bash > > ./pharo Pharo.image save $JOB_NAME > > REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main > ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development > ./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" > ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*" > > mv ./pharo-vm/PharoV20.sources ./ > zip -r $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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
However, the build is still red, for a different although
Alexandre > Le 28-01-2014 à 11:11, Alexandre Bergel <[hidden email]> a écrit : > > Thanks! > This is great! > > Native Boost does something that requires the author name > > Alexandre > > >> On Jan 28, 2014, at 7:09 AM, Tudor Girba <[hidden email]> wrote: >> >> The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests. >> >> >> Here is the new script: >> >> ---- >> wget --quiet -O - http://get.pharo.org/30+vm | bash >> >> ./pharo Pharo.image save $JOB_NAME >> >> REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main >> ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development >> ./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" >> ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*" >> >> mv ./pharo-vm/PharoV20.sources ./ >> zip -r $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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > 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 |
|
|
The build of Moose I meant. Roassal 2 is still yellow now. We will fix it...
Alexandre > Le 28-01-2014 à 11:47, Alexandre Bergel <[hidden email]> a écrit : > > However, the build is still red, for a different although > > Alexandre > >> Le 28-01-2014 à 11:11, Alexandre Bergel <[hidden email]> a écrit : >> >> Thanks! >> This is great! >> >> Native Boost does something that requires the author name >> >> Alexandre >> >> >>> On Jan 28, 2014, at 7:09 AM, Tudor Girba <[hidden email]> wrote: >>> >>> The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests. >>> >>> >>> Here is the new script: >>> >>> ---- >>> wget --quiet -O - http://get.pharo.org/30+vm | bash >>> >>> ./pharo Pharo.image save $JOB_NAME >>> >>> REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main >>> ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development >>> ./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" >>> ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*" >>> >>> mv ./pharo-vm/PharoV20.sources ./ >>> zip -r $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 >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> 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 |
Re: roassal2 job sets the author
|
|
As I said previously, the Moose build is red because of a bug in Pharo related to loading Traits. Doru On Tue, Jan 28, 2014 at 3:48 PM, Alexandre Bergel <[hidden email]> wrote: The build of Moose I meant. Roassal 2 is still yellow now. We will fix it... "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Wait, all Moose-dependant projects are red because Pharo has traits problem?
Uko On 28 Jan 2014, at 16:27, Tudor Girba <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: roassal2 job sets the author
|
|
Yes. You cannot load a package containing Traits in Pharo now. And Moose-Algos relies on Traits. So, if you load the Moose code from scratch, the build will be red. Doru On Wed, Jan 29, 2014 at 1:03 AM, Yuriy Tymchuk <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |