Hi!
I do not understand. Apparently Roassal2 cannot be build. Any idea why? Alexandre On Jan 24, 2014, at 7:13 PM, [hidden email] wrote: > See <https://ci.inria.fr/moose/job/roassal2/41/> > > ------------------------------------------ > [URLTrigger] A change within the response URL invocation (log) > Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/roassal2/ws/> > > Deleting project workspace... done > > [roassal2] $ /bin/sh -xe /tmp/hudson7964457589234081262.sh > + wget --quiet -O - http://get.pharo.org/30+vm > + bash > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > + ./pharo Pharo.image save roassal2 > + REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main > + ./pharo roassal2.image config http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ConfigurationOfRoassal2 --install=development > [31m[33m > =============================================================================== > Notice: Installing ConfigurationOfRoassal2 development > =============================================================================== > [0m[0mInstalling ConfigurationOfRoassal2 development > > Loading dev of ConfigurationOfRoassal2... > Fetched -> Trachel-AlexandreBergel.57 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Fetched -> Roassal2-JurajKubelka.91 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Loaded -> Trachel-AlexandreBergel.57 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > RTDowserExample>>example6 (ROObject is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > Loaded -> Roassal2-JurajKubelka.91 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > ...finished dev+ ./pharo roassal2.image test --junit-xml-output Roassal2.*|Trachel.* > [31m[33m > =============================================================================== > Notice: Running tests in 2 Packages > =============================================================================== > [0m[0mRunning tests in 2 Packages > [31mAn attempt to use interactive tools detected, while in non-interactive mode > Interactive Request: [ Author identification ] Please type your full name. > It will be used to sign the changes you make to the image. > Spaces, accents, dashes, underscore and similar characters are not allowed > > [0mNonInteractiveUIManager>>nonInteractiveWarning: > NonInteractiveUIManager>>nonInteractiveRequest:title: > NonInteractiveUIManager>>request:initialAnswer:title:entryCompletion: > NonInteractiveUIManager>>request:initialAnswer:title: > AuthorNameRequest>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > AuthorNameRequest(Exception)>>signal > Author>>requestFullName > Author>>fullName > Author class>>fullName > Author class>>changeStamp > SQSurfaceDispatch class(ClassDescription)>>compile:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: in Block: [ self compile: code classified: category notifyin...etc... > BlockClosure>>ensure: > SystemAnnouncer>>suspendAllWhile: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified: > SQSurfaceDispatch class(NBExternalStructure class)>>createAccessorsFor: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors in Block: [ :fldName | self createAccessorsFor: fldName ] > NBExternalStructureFields>>fieldNamesDo: in Block: [ :name | aBlock value: name ] > Dictionary>>keysDo: in Block: [ :association | aBlock value: association key ] > Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock value: each ] ] > Array(SequenceableCollection)>>do: > Dictionary>>associationsDo: > Dictionary>>keysDo: > NBExternalStructureFields>>fieldNamesDo: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors > SQSurfaceDispatch class(NBExternalStructure class)>>fields > [0mBuild step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
CONTENTS DELETED
The author has deleted this message.
|
Jenkins is really not that complicated. The first thing you do when you see a failed build is go to the output console: There you will see: =============================================================================== Notice: Running tests in 2 Packages =============================================================================== [0m[0mRunning tests in 2 Packages [31mAn attempt to use interactive tools detected, while in non-interactive mode Interactive Request: [ Author identification ] Please type your full name. It will be used to sign the changes you make to the image. Spaces, accents, dashes, underscore and similar characters are not allowed [0mNonInteractiveUIManager>>nonInteractiveWarning: This means that your tests do something that requires an explicit author. Cheers, Doru On Fri, Jan 24, 2014 at 11:39 PM, Juraj Kubelka <[hidden email]> wrote: I do not know if it is the problem, but I have removed right now the dependencies on Roassal1. "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
I saw that, but I always thought that your script set an author. So this is not the case? Alexandre
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi, No it's not the case. But, why should it? Doru On Sun, Jan 26, 2014 at 1:13 PM, Alexandre Bergel <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Here is the script used: -------- 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 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 On Sun, Jan 26, 2014 at 1:58 PM, Tudor Girba <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |