Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Build failed in Jenkins: moose-latest-dev-4.9 #1299
by admin＠moosetechnology.org 19 Oct '13

19 Oct '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1299/> ------------------------------------------ Started by upstream project "glamour" build number 349 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.9/ws/> Deleting project workspace... done [moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson4618962989300060370.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.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 moose-latest-dev-4.9 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./pharo moose-latest-dev-4.9.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1299/ [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

1 0

Build failed in Jenkins: moose-latest-dev-4.9 #1297
by admin＠moosetechnology.org 19 Oct '13

19 Oct '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1297/> ------------------------------------------ [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.9/ws/> Deleting project workspace... done [moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson8805368009257370614.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.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 moose-latest-dev-4.9 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m[33m *** Warning: Warning: This package depends on the following classes: MOViewRenderer You must resolve these dependencies before you will be able to load these definitions: edgesDsm:from:to: [0m[0m+ ./pharo moose-latest-dev-4.9.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1297/ [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

1 0

Issue 988 in moose-technology: Moose-algos build is green
by moose-technology＠googlecode.com 18 Oct '13

18 Oct '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 988 by anne.et...(a)gmail.com: Moose-algos build is green http://code.google.com/p/moose-technology/issues/detail?id=988 Moose-algos package needs some cleaning. Look at the tests failing in the build on jenkins. -- 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

3 3

Issue 890: All meta-entities should have a class comment
by Anne Etien 18 Oct '13

18 Oct '13

Hi, During our MooseSprint, we wanted to add the missing comments, but we do not see which meta-entities do not have comment. All the classes inheriting from FamixEntity have comments. Nevertheless, some other classes in FamixCore do not have comment. Were you talking about these classes? Can you please give more information? Thanks, Anne

2 1

Issue 989 in moose-technology: MoosePanel search should not throw error
by moose-technology＠googlecode.com 18 Oct '13

18 Oct '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Finder New issue 989 by anne.et...(a)gmail.com: MoosePanel search should not throw error http://code.google.com/p/moose-technology/issues/detail?id=989 When searching in MoosePanel through queries, there are DNU exceptions that should be caught. -- 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

1 0

Roassal animations
by Yuriy Tymchuk 17 Oct '13

17 Oct '13

Hi, what do you thing about replacing ROPluggableAnimation's>>doStep `block value` with `block cull: self elapsedCycles`? Because this way you can have a block hooked to the number of cycle. Cheers. Uko

4 8

[ann] system attraction view
by Tudor Girba 17 Oct '13

17 Oct '13

Hi, I built a new visualization that has two goals: 1. show how the architecture of a system is fluid rather than rigid. 2. look good and serve as advertisement device for Moose, Roassal and Pharo. A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/ I already used it as a splash screen for a couple of presentations, and it catches the eye. The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

5 10

[Roassal] Tree Map Builder Cont'd
by roberto.minelli＠usi.ch 16 Oct '13

16 Oct '13

Hi, I just committed in RoassalExtra a new example of the tree map builder that shows how to create dynamic tree maps. There is still some work to do, but in the meantime... Check it out @ https://dl.dropboxusercontent.com/u/6281855/DynamicTreeMap.mov Cheers, Roby

2 1

Rectangle packing layout
by Yuriy Tymchuk 16 Oct '13

16 Oct '13

Hi everyone! You know, some times you have a pile of different rectangles representing some entities. And you want to show them to someone so that he can take a look at them to assess something. But there is always a question how do you arrange this rectangles? Usually it's not practical to place them in a line or in a circle because it takes too much space. I've developed a layout that tries to pack rectangles in a compact space, and here is how it looks like: You can load it into your image with: Gofer new smalltalkhubUser: 'YuriyTymchuk' project: 'RecPack-Layout'; package: 'RecPack-Layout'; load. and you can see a couple of examples in Roassal easel. Feedback is appreciated. Cheers! Uko

8 17

Closing Roassal windows with cmd+w
by Yuriy Tymchuk 16 Oct '13

16 Oct '13

Hi everyone, one thing that I like to do with windows is to close them with cmd+w shortcut. Sadly Roassal windows does not allow that. Do you know if it's hard to implement? Cheers. uko

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev