Dear all,
I have now a travis job running for Moose here: https://travis-ci.org/moosetechnology/Moose/jobs/147971040 with the same tests than on Jenkins: https://ci.inria.fr/moose/job/moose-6.0/
But strangely, there is some errors on the travis job that do not appear on Jenkins. listBackgroundColor message is send to Pharo3Theme, but there is no message like that in Pharo 5.0 …
Any ideas why ?
No idea why. Do you have the same base image?
Anyway, having moose on travis is interesting. What does it bring more than Jenkins? Just wondering.
Alexandre
On Jul 28, 2016, at 7:19 AM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Dear all,
I have now a travis job running for Moose here: https://travis-ci.org/moosetechnology/Moose/jobs/147971040 with the same tests than on Jenkins: https://ci.inria.fr/moose/job/moose-6.0/
But strangely, there is some errors on the travis job that do not appear on Jenkins. listBackgroundColor message is send to Pharo3Theme, but there is no message like that in Pharo 5.0 …
Any ideas why ?
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Le 28/7/16 à 20:19, Alexandre Bergel a écrit :
No idea why. Do you have the same base image?
Anyway, having moose on travis is interesting. What does it bring more than Jenkins? Just wondering.
integration with git. since there is a free online service no need to have inria like service.
Stef
Alexandre
On Jul 28, 2016, at 7:19 AM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Dear all,
I have now a travis job running for Moose here: https://travis-ci.org/moosetechnology/Moose/jobs/147971040 with the same tests than on Jenkins: https://ci.inria.fr/moose/job/moose-6.0/
But strangely, there is some errors on the travis job that do not appear on Jenkins. listBackgroundColor message is send to Pharo3Theme, but there is no message like that in Pharo 5.0 …
Any ideas why ?
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Ok! Thanks!
Alexandre
On Jul 28, 2016, at 4:08 PM, stepharo stepharo@free.fr wrote:
Le 28/7/16 à 20:19, Alexandre Bergel a écrit :
No idea why. Do you have the same base image?
Anyway, having moose on travis is interesting. What does it bring more than Jenkins? Just wondering.
integration with git. since there is a free online service no need to have inria like service.
Stef
Alexandre
On Jul 28, 2016, at 7:19 AM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Dear all,
I have now a travis job running for Moose here: https://travis-ci.org/moosetechnology/Moose/jobs/147971040 with the same tests than on Jenkins: https://ci.inria.fr/moose/job/moose-6.0/
But strangely, there is some errors on the travis job that do not appear on Jenkins. listBackgroundColor message is send to Pharo3Theme, but there is no message like that in Pharo 5.0 …
Any ideas why ?
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
On Thu, Jul 28, 2016 at 10:08 PM, stepharo stepharo@free.fr wrote:
Le 28/7/16 à 20:19, Alexandre Bergel a écrit :
No idea why. Do you have the same base image?
Anyway, having moose on travis is interesting. What does it bring more than Jenkins? Just wondering.
integration with git. since there is a free online service no need to have inria like service.
Yes this is the idea :-)
Moose build job loads more stuff than just Moose.
./pharo moose-6.0.image eval Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamourCore'; load. Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGTInspector'; package: 'ConfigurationOfGTInspectorCore'; package: 'ConfigurationOfGTSpotter'; package: 'ConfigurationOfGTPlayground'; package: 'ConfigurationOfGTPlaygroundCore'; package: 'ConfigurationOfGToolkit'; package: 'ConfigurationOfGToolkitCore'; package: 'ConfigurationOfGTEventRecorder'; load. Smalltalk snapshot: true andQuit: true. ./pharo moose-6.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
I don't know if that's the issue, but it might be worth looking into.
Btw if you are running travis job just because you need it as a baseline image, you can use Moose directly with SmalltalkCI: https://github.com/hpi-swa/smalltalkCI#list-of-supported-images
Peter
On Thu, Jul 28, 2016 at 02:19:38PM -0400, Alexandre Bergel wrote:
No idea why. Do you have the same base image?
Anyway, having moose on travis is interesting. What does it bring more than Jenkins? Just wondering.
Alexandre
On Jul 28, 2016, at 7:19 AM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Dear all,
I have now a travis job running for Moose here: https://travis-ci.org/moosetechnology/Moose/jobs/147971040 with the same tests than on Jenkins: https://ci.inria.fr/moose/job/moose-6.0/
But strangely, there is some errors on the travis job that do not appear on Jenkins. listBackgroundColor message is send to Pharo3Theme, but there is no message like that in Pharo 5.0 …
Any ideas why ?
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
On Thu, Jul 28, 2016 at 11:27 PM, Peter Uhnak i.uhnak@gmail.com wrote:
Moose build job loads more stuff than just Moose.
./pharo moose-6.0.image eval Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamourCore'; load. Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGTInspector'; package: 'ConfigurationOfGTInspectorCore'; package: 'ConfigurationOfGTSpotter'; package: 'ConfigurationOfGTPlayground'; package: 'ConfigurationOfGTPlaygroundCore'; package: 'ConfigurationOfGToolkit'; package: 'ConfigurationOfGToolkitCore'; package: 'ConfigurationOfGTEventRecorder'; load. Smalltalk snapshot: true andQuit: true. ./pharo moose-6.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
I don't know if that's the issue, but it might be worth looking into.
yes you are right ... Why the MOOSE Configuration is not loading everything ?
Btw if you are running travis job just because you need it as a baseline image, you can use Moose directly with SmalltalkCI: https://github.com/hpi-swa/smalltalkCI#list-of-supported-images
Yes I know, but here I try to build MOOSE image: https://github.com/moosetechnology/Moose
-
Alexandre Bergel -
Peter Uhnak -
Serge Stinckwich -
stepharo