Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/184/> ------------------------------------------ Started by upstream project "gtoolkit" build number 24 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/hudson7959591288962466457.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.0DT4g/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 [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

12 years

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/179/> ------------------------------------------ Started by upstream project "fame" build number 14 originally caused by: Started by user tudor(a)tudorgirba.com 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/hudson8490378866447075765.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

12 years

Issue 924 in moose-technology: VerveineJ does not export isWrite flags for accesses

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.8 New issue 924 by tu...(a)tudorgirba.com: VerveineJ does not export isWrite flags for accesses http://code.google.com/p/moose-technology/issues/detail?id=924 isWrite should be populated for every access to a variable residing on the left hand side of an assignment. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

12 years

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/177/> ------------------------------------------ Started by upstream project "gtoolkit" build number 22 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/hudson6200527060324890121.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

12 years

Broken method GlamourousHealth>>produceReport

by Juraj Kubelka

Hi, there is class GlamourousHealth which apparently is not used. Command GlamourousHealth new produceReport. produces some errors (at least missing message GLMFinder>>list). Is it used? Should we remove it? Or fix it? Thank you a lot, Jura

12 years

Jenkins build became unstable: moose-latest-dev-4.8 #160

by admin＠moosetechnology.org

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

12 years

#pharoconf #mooseday on twitter

by Tudor Girba

Hi, If you want to tweet/follow what is going on at PharoConf and MooseDay, please use #pharoconf and #mooseday. Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

12 years

Jenkins build is back to stable : moose-latest-dev-4.8 #168

by admin＠moosetechnology.org

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

12 years

new version of the (old) versionner

by Alexandre Bergel

Hi! In the meantime we have a reliable solution to manage configuration, I have updated http://squeaksource.com/Versionner.html The two most significant changes are: - SmalltalkHub is now supported - Committing a project now produces a stable version (instead of a development) and the most recent baseline is marked as #development. In the meantime to have Versionner2 around, I worked a bit on Versionner to solve some pressing issues with Moose. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years

Re: SmalltalkHub and Versionner

by Alexandre Bergel

> If you want to use Versionner on Pharo1.4 with SmalltalkHub, there is no problem. You just need to declare an http repository: > MCHttpRepository > location: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal/main' > user: '' > password: '' Thanks, it works fine >> @Christophe: what is needed to have Versionner working on Pharo 2.0. > > > I still have work to be able to edit existing configurations (add packages, projects, ...) but "old" Versionner commands are still there. > The biggest issue I have with Pharo2 is MetacelloToolBox. > Metacello have been ported to Pharo2 but not MetacelloTests (despite this, it seems to work quite fine). > Metacello Toolbox shipped with Pharo2 is not working because it comes from another branch than Metacello core (different behavior, methods missing). > I planned to work on this point next week with Esteban. > Once done, I just need to check that we do not have issues with announcements (biggest change for Versionner between pharo 1.4 and 2.0). > > To resume, to have the "old" Versionner working, the point is to fix MetacelloToolbox in Pharo2 and check announcements. > I will see with Esteban if we can start this work earlier (have Metacello tests green in Pharo2, update the toolbox). > I hope to have good news on this front very soon because I also decided to give up Pharo 1.4 for dev. We have Pharo2 and now Pharo3 on the road, I cannot use anymore on old version. > > Is it fine for you? Yes, it looks like to be okay. Thanks for this update Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev