Build failed in Jenkins: moose-latest-dev-4.8 #171 - Moose-dev

admin＠moosetechnology.org

1 Apr 1 Apr

9:56 p.m.

New subject: Build failed in Jenkins: moose-latest-dev-4.8 #172

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/172/> ------------------------------------------ [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/hudson6690320270574079452.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip image.24106/Pharo-20594.image bash: line 70: syntax error near unexpected token `newline' Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results

Reply

admin＠moosetechnology.org

2 Apr 2 Apr

12:26 a.m.

New subject: Jenkins build is back to normal : moose-latest-dev-4.8 #174

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

Reply

Tudor Girba

6:39 a.m.

New subject: Build failed in Jenkins: moose-latest-dev-4.8 #173

Could it be that the problem comes from you not being logged in? Cheers, Doru On Apr 2, 2013, at 1:50 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:

...

Sorry guys about that. We have problem to access SmalltalkHub. Times to times, half of the packages are saved... I guess this comes from the connection we have. Cheers, Alexandre On Apr 1, 2013, at 5:54 PM, admin(a)moosetechnology.org wrote:

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/173/> ------------------------------------------ Started by upstream project "roassal" build number 38 originally caused by: [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/hudson2372356051012870995.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh 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 vm.sh and vm-ui.sh 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 [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [31m==== Startup Error: ConnectionTimedOut: Data receive timed out. [0mSocket>>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... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Data receive timed out. [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

Reply

stephane ducasse

7 Apr 7 Apr

5:01 p.m.

New subject: Build failed in Jenkins: moose-latest-dev-4.8 #173

can you check to incorporate the fix that sven issued for the university of bern? I'm not 100% is was integrated to 2.0.1 On Apr 2, 2013, at 3:52 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:

...

Could it be that the problem comes from you not being logged in?

No. Probably something is going wrong in the internet provider of the university of chile Alexandre

On Apr 2, 2013, at 1:50 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:

Sorry guys about that. We have problem to access SmalltalkHub. Times to times, half of the packages are saved... I guess this comes from the connection we have. Cheers, Alexandre On Apr 1, 2013, at 5:54 PM, admin(a)moosetechnology.org wrote:

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/173/> ------------------------------------------ Started by upstream project "roassal" build number 38 originally caused by: [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/hudson2372356051012870995.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh 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 vm.sh and vm-ui.sh 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 [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [31m==== Startup Error: ConnectionTimedOut: Data receive timed out. [0mSocket>>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... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Data receive timed out. [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply