Moose-dev February 2013

moose-dev@list.inf.unibe.ch

21 participants
145 discussions

Moose loaded on Pharo 2.0
by Nicolas Anquetil 22 Feb '13

22 Feb '13

tests are red :-) (not that much because we only took Moose-Ttests*) 1005 run, 969 passes, 0 skipped, 1 expected failures, 13 failures, 22 errors, 0 unexpected passes nicolas -- Nicolas Anquetil -- RMod research team (Inria)

1 0

glamour moved
by Usman Bhatti 22 Feb '13

22 Feb '13

I moved glamour to STHub - config updated to create a baseline for pharo1.4 pointing to STHub for as many packages as possible (roassal, Metacello, BDD is still in SS) - loaded the baseline in 1.4 pharo...all tests green... - created a baseline for pharo 2.0...loaded in 2.0 and ran tests, here are the results: 357 run, 246 passes, 0 skipped, 12 expected failures, 0 failures, 99 errors, 0 unexpected passes - I wanted to define #stable and #development but since these are already defined with specific version info, I didn't modify these. Doru, can you have look for the definition of symbolic versions?

1 0

glamour in the course of being migrated
by Tudor Girba 22 Feb '13

22 Feb '13

Hi, I started to migrate Glamour to SmalltalkHub. Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought."

4 19

Jenkins build became unstable: moose-latest-dev #1287
by address not configured yet 21 Feb '13

21 Feb '13

See <http://localhost:8020/job/moose-latest-dev/1287/>

2 2

Fwd: [Pharo-project] Time Series in Smalltalk
by stephane ducasse 21 Feb '13

21 Feb '13

I thought that we had something like that in Moose. Begin forwarded message: > From: Serge Stinckwich <serge.stinckwich(a)gmail.com> > Subject: [Pharo-project] Time Series in Smalltalk > Date: February 20, 2013 10:28:10 PM GMT+01:00 > To: Pharo Development <pharo-project(a)lists.gforge.inria.fr> > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Hi all, > > I'm looking for a time series library available in Smalltalk. > Something like Python Time Series Analysis : http://pytseries.sourceforge.net/ > or > Pandas: http://pandas.pydata.org/ > > Thank you. > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

1 0

config of moose on SThub
by Usman Bhatti 21 Feb '13

21 Feb '13

I sent this mail yesterday but strangely no received it, so here it is again. With Nicolas, we have created a first baseline of Moose based on the projects in STHub. The baseline baseline47STHub: corresponds to the old core-default baseline. Loading the baseline on 1.4 works fine, here are the test results: 998 run, 991 passes, 1 expected failures, 6 failures, 0 errors, 0 unexpected passes For each proj moved to SThub, we have tried to define two symbolic versions: #stable: a specific version of a proj at the time of move to STHub #bleedingEdge: load the latest packages of a proj.

4 8

when do we release 4.8?
by Stéphane Ducasse 19 Feb '13

19 Feb '13

Hi doru What is blocking the release of 4.8? Because it would be good to release Moose 4.8 as the version before migrating to STHUB then we can work on having a version running on Pharo 2.0. Stef

5 7

Build failed in Jenkins: moose-latest-dev #1284
by address not configured yet 17 Feb '13

17 Feb '13

See <http://localhost:8020/job/moose-latest-dev/1284/> ------------------------------------------ Started by timer Building in workspace <http://localhost:8020/job/moose-latest-dev/ws/> [workspace] $ /bin/sh -xe /tmp/hudson141875937493458092.sh + rm -rf <http://localhost:8020/job/moose-latest-dev/ws/moose> <http://localhost:8020/job/moose-latest-dev/ws/moose-tests> + /srv/ci.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s monticello-fix-for-14 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose [31m[33m =============================================================================== Notice: Errors in script loaded from <http://localhost:8020/job/moose-latest-dev/1284/artifact/moose/moose.st> =============================================================================== [0m[0m[31m==== Startup Error: GoferRepositoryError: Could not access http://www.squeaksource.com/glamoroust: ConnectionTimedOut: Cannot connect to 130.92.64.38:80 [0mMCHttpRepository(MCFileBasedRepository)>>goferReferences in Block: [:error | ^ GoferRepositoryError signal: error mes...etc... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [(self tempAt: 2)... BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: [0m[31mGot startup errors: [0m[31m GoferRepositoryError: Could not access http://www.squeaksource.com/glamoroust: ConnectionTimedOut: Cannot connect to 130.92.64.38:80 [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build.sh -i moose -s patch-inputsensor -s testrunner -s moose-tests -o moose-tests [31m[33m =============================================================================== Notice: Errors in script loaded from <http://localhost:8020/job/moose-latest-dev/ws/moose-tests/moose-tests.st> =============================================================================== [0m[0m[31m==== Startup Error: MessageNotUnderstood: receiver of "new" is nil [0mUndefinedObject(Object)>>doesNotUnderstand: #new UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [| chunk | val := (self peekFor: $!)... BlockClosure>>on:do: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [:bar | ... NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: receiver of "new" is nil [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build-oneclick.sh -i moose -o moose_suite-4_7_dev -n Moose -t 'Moose Suite 4.7 Development ' -v 4.7 -c Moose cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.png': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.ico': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.icns': No such file or directory /srv/ci.moosetechnology.org/builder/build-oneclick.sh: line 170: zip: command not found Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE Archiving artifacts

1 1

moved Moose-Algos
by Usman Bhatti 17 Feb '13

17 Feb '13

Moose-Algos is moved to SThub. Created a new baseline that loads from SThub. Create a bleedingEdge symbolic version that loads the latest dev Created a version in #stable for both 1.4 and pharo 2.0. For pharo1.4-> All tests green For pharo 2.0- > All tests green

2 1

Filtering elements to import from MSE files?
by Hani Abdeen 15 Feb '13

15 Feb '13

Hi, I'm wondering if it's possible to configure the MSE importer of Moose to import elements that satisfy some conditions (e.g., [ :element | element isFamixPackage ]). In fact, I need to import only packages/namespaces and their classes from MSE files. Why? because I want to load many many moose models (software versions) in one image and I'm interested in few information within those models (e.g., packages and their classes --without methods, attributes, references, invocations, etc.). By reading FMMSEParser and FMParseClientFilter, I found that we may set a filter that specify the name of elements to import. Yet I'm not sure about this. However, I did not find any api that we may use to set a filter that specify the type of elements to import. Is there a such api? if no, is it "possible" to implement it? any suggestions? It would be great if we can set a block filter: e.g., [ :element | element isFamixScopingEntity and: [ element isStub not ] ] Cheers, Hani

3 5

← Newer
1
...
9
10
11
12
13
14
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2013