Build failed in Jenkins: moose-latest-dev-4.8 #188

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Build failed in Jenkins: moose-latest-dev-4.8 #188

admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/188/>

------------------------------------------
Started by upstream project "gtoolkit" build number 27
originally caused by:
[URLTrigger] A change within the response URL invocation (log)
[URLTrigger] A change within the response URL invocation (log)
Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>

Deleting project workspace... done

[moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson7168353918600658867.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
    http://files.pharo.org/image/20/latest.zip
image.9hKzH/Pharo-20596.image
Downloading the latest pharoVM:
        http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
vm/pharo
Downloading PharoV10.sources:
        http://files.pharo.org/image//PharoV10.sources.zip
Downloading PharoV20.sources:
        http://files.pharo.org/image//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
Please install the 32bit libraries
   sudo aptitude install ia32-libs
+ ./vm.sh Pharo.image save moose-latest-dev-4.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development

===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup
==== Startup Error: ConnectionTimedOut: Data receive timed out.
Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
Socket>>waitForDataFor:ifClosed:ifTimedOut:
Socket>>waitForDataFor:
Socket>>receiveDataSignallingTimeout:into:startingAt:
SocketStream>>receiveData
SocketStream>>next
ZnLineReader>>processNext
ZnLineReader>>nextLine
ZnStatusLine>>readFrom:
ZnStatusLine class>>readFrom:
ZnResponse>>readHeaderFrom:
ZnResponse(ZnMessage)>>readFrom:
ZnResponse class(ZnMessage class)>>readFrom:
ZnClient>>executeRequestResponse
ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse]
BlockClosure>>ensure:
ZnClient>>getConnectionAndExecute
ZnClient>>executeWithRedirectsRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc...
BlockClosure>>on:do:
ZnClient>>executeWithRetriesRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0...
BlockClosure>>cull:
MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
ConnectionTimedOut(Exception)>>signal
ConnectionTimedOut(Exception)>>signal:
ConnectionTimedOut class(Exception class)>>signal:
Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
Got startup errors:
    ConnectionTimedOut: Data receive timed out.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Build failed in Jenkins: moose-latest-dev-4.8 #188

Tudor Girba-2
I found out what the problem was:
My server was offline due to some provider outage, and the build failed when retrieving the Moose logo :)

It should work now.

Cheers,
Doru


On Apr 2, 2013, at 9:34 PM, [hidden email] wrote:

> See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/188/>
>
> ------------------------------------------
> Started by upstream project "gtoolkit" build number 27
> originally caused by:
> [URLTrigger] A change within the response URL invocation (log)
> [URLTrigger] A change within the response URL invocation (log)
> Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/>
>
> Deleting project workspace... done
>
> [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson7168353918600658867.sh
> + bash
> + wget --quiet -O - http://get.pharo.org/20+vmLatest
> Downloading the latest 20 Image:
>    http://files.pharo.org/image/20/latest.zip
> image.9hKzH/Pharo-20596.image
> Downloading the latest pharoVM:
> http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip
> vm/pharo
> Downloading PharoV10.sources:
> http://files.pharo.org/image//PharoV10.sources.zip
> Downloading PharoV20.sources:
> http://files.pharo.org/image//PharoV20.sources.zip
> Creating starter scripts pharo and pharo-ui
> Please install the 32bit libraries
>   sudo aptitude install ia32-libs
> + ./vm.sh Pharo.image save moose-latest-dev-4.8
> + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
> + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
> 
> ===============================================================================
> Notice: Installing ConfigurationOfMoose development
> ===============================================================================
> + ./vm.sh moose-latest-dev-4.8.image mooseimagesetup
> ==== Startup Error: ConnectionTimedOut: Data receive timed out.
> Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
> Socket>>waitForDataFor:ifClosed:ifTimedOut:
> Socket>>waitForDataFor:
> Socket>>receiveDataSignallingTimeout:into:startingAt:
> SocketStream>>receiveData
> SocketStream>>next
> ZnLineReader>>processNext
> ZnLineReader>>nextLine
> ZnStatusLine>>readFrom:
> ZnStatusLine class>>readFrom:
> ZnResponse>>readHeaderFrom:
> ZnResponse(ZnMessage)>>readFrom:
> ZnResponse class(ZnMessage class)>>readFrom:
> ZnClient>>executeRequestResponse
> ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse]
> BlockClosure>>ensure:
> ZnClient>>getConnectionAndExecute
> ZnClient>>executeWithRedirectsRemaining:
> ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc...
> BlockClosure>>on:do:
> ZnClient>>executeWithRetriesRemaining:
> ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0...
> BlockClosure>>cull:
> MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
> BlockClosure>>ensure:
> MethodContext(ContextPart)>>handleSignal:
> ConnectionTimedOut(Exception)>>signal
> ConnectionTimedOut(Exception)>>signal:
> ConnectionTimedOut class(Exception class)>>signal:
> Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
> Got startup errors:
>     ConnectionTimedOut: Data receive timed out.
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Recording test results
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Be rather willing to give than demanding to get."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Jenkins build is back to normal : moose-latest-dev-4.8 #189

admin-2
In reply to this post by admin-2
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/189/>

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev