Hi Alexandre,
The stack trace of your email seems not related to the current error. It is a problem with
Sthub. It seems to happened randomly.
The current problem is due to the fact that the email addresses where to send the failure
or success mails are not well filled. You should put directly your email i.e.
"moose-dev@iam.unibe.ch<mailto:moose-dev@iam.unibe.ch>" and not the
displayed name i.e. "Moose-related development
moose-dev@iam.unibe.ch<mailto:moose-dev@iam.unibe.ch>".
I corrected it.
Now, it seems that the PharoV30.sources are missing...
Cheers,
Vincent
De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de
Alexandre Bergel
Envoyé : mercredi 15 avril 2015 17:01
À : Moose-related development
Objet : [Moose-dev] Fwd: Build failed in Jenkins: roassal2 #1386
Any idea why the build fail?
Is it a problem of smalltalkhub? Recently, I got some errors when committing in a repo.
Weird errors such as: wrongly defined http request (I do not remember the exact message).
Errors usually occurs with a poor internet connection.
Am I the only one to experience this?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Begin forwarded message:
From: admin@moosetechnology.org<mailto:admin@moosetechnology.org>
Date: April 15, 2015 at 11:47:15 AM GMT-3
To: Alexandre@mac.com<mailto:Alexandre@mac.com>,
Bergel@mac.com<mailto:Bergel@mac.com>,
alexandre.bergel@me.com<mailto:alexandre.bergel@me.com>,
tudor@tudorgirba.com<mailto:tudor@tudorgirba.com>
Subject: Build failed in Jenkins: roassal2 #1386
See <https://ci.inria.fr/moose/job/roassal2/1386/>
------------------------------------------
[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/hudson2786734544130023094.sh
+ + bash
wget --quiet -O -
http://get.pharo.org/40+vm
Downloading the latest 40 Image:
http://files.pharo.org/get-files/40/pharo.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/get-files/40/pharo-linux-stable.zip
pharo-vm/pharo
Downloading PharoV40.sources:
http://files.pharo.org/get-files/40/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
'Installing ConfigurationOfRoassal2 development'
[31m==== Startup Error: Error: Could not load
ConfigurationOfRoassal2-AlexandreBergel.30.mcz: ZnHttpUnsuccessful: 400 Bad Request
[0mMCSmalltalkhubRepository(Object)>>error:
[ :exception | self error: 'Could not load ' , aString , ': ' , exception
printString ] in [
client := self httpClient.
client
ifFail: [ :exception | self error: 'Could not load ' , aString ,
': ' , exception printString ];
get: (self urlForFileNamed: aString).
self assertBinaryResponse: client response. "immediately cache the version and
avoid an unnecessary serialization"
self cacheRawVersionNamed: aString stream: client contents ] in
MCSmalltalkhubRepository(MCHttpRepository)>>readStreamForFileNamed:do: in Block: [
:exception | self error: 'Could not load ' , aSt...etc...
BlockClosure>>cull:
Context>>evaluateSignal:
Context>>handleSignal:
Context>>handleSignal:
ZnHttpUnsuccessful(Exception)>>signal
ZnClient>>handleResponse
ZnClient>>executeWithRedirectsRemaining:
[ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in
ZnClient>>executeWithRetriesRemaining: in Block: [ self
executeWithRedirectsRemaining: self maxNumb...etc...
BlockClosure>>on:do:
ZnClient>>executeWithRetriesRemaining:
[ self executeWithRetriesRemaining: self numberOfRetries ] in [
[ self executeWithRetriesRemaining: self numberOfRetries ]
on: Error
do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ self
executeWithRetriesRemaining: self numberOfR...etc...
BlockClosure>>on:do:
[
[ self executeWithRetriesRemaining: self numberOfRetries ]
on: Error
do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ ...
[ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value ]
[
p psValueAt: index put: anObject.
aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: in Block: [
...
BlockClosure>>ensure:
ZnConnectionTimeout(DynamicVariable)>>value:during:
ZnConnectionTimeout class(DynamicVariable class)>>value:during:
ZnClient>>withTimeoutDo:
ZnClient>>executeWithTimeout
[ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ result :=
self executeWithTimeout ]
[ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block value ]
[
p psValueAt: index put: anObject.
aBlock value ] in ZnSignalProgress(DynamicVariable)>>value:during: in Block: [ ...
BlockClosure>>ensure:
ZnSignalProgress(DynamicVariable)>>value:during:
ZnSignalProgress class(DynamicVariable class)>>value:during:
ZnClient>>withProgressDo:
ZnClient>>execute
[0m[31mGot startup errors:
[0m[31m Error: Could not load ConfigurationOfRoassal2-AlexandreBergel.30.mcz:
ZnHttpUnsuccessful: 400 Bad Request
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
________________________________
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de
ses destinataires. Il peut également être protégé par le secret professionnel. Si vous
recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de
le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la
responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien
que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout
virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne
saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the
addressee; it may also be privileged. If you receive this e-mail in error, please notify
the sender immediately and destroy it. As its integrity cannot be secured on the Internet,
the Worldline liability cannot be triggered for the message content. Although the sender
endeavours to maintain a computer virus-free network, the sender does not warrant that
this transmission is virus-free and will not be liable for any damages resulting from any
virus transmitted.