MooseDay in Lille
by Anne Etien
Hi,
In order to start the organization of the MooseDay in Lille, we would like to know, who would be interested in attending and who would like to make a presentation. The idea would be to organize it the first or the second week of October.
Please let us know your interest in the MooseDay in Lille (France).
Thanks in advance.
Anne
10 years, 1 month
Re: persisting moose models
by Stephan Eggermont
Hi Fabrizio,
Moose models are highly interconnected, and the analyzing algorithms tend to touch
a lot of other objects. There is very limited locality of reference, so a RDBMS (or NoSQL)
cannot help you here. You basically would only be swapping in and out objects.
Stephan
10 years, 1 month
looking at the frozen spec
by Stéphane Ducasse
Hi doru
while reloading/retrying I looked the generated spec and I noted some points that may reveal missing dependencies
* #('Famix-Tests-C-AndreHora.6.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Famix-Tests-C' )
#('Famix-Tests-Extensions-TudorGirba.23.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Famix-Tests-Extensions' )
#('Dynamix-Tests-Core-TudorGirba.17.mcz' 'http://www.smalltalkhub.com/mc/Moose/DynaMoose/main/' 'Dynamix-Tests-Core' )
arrive quite earrly even before magritte fame….
Now I found some bugs in Moose configurations:
Problem 1
--------------
* Moose-Hismo arrives before FAMIX-Core.
And this is false.
This package depends on the following classes:
FAMIXPackage
FAMIXEntity
FAMIXInheritance
You must resolve these dependencies before y
So I cannot reload our application (our application is simple is basically only depend on Moose and PetitParser. I checked all the
configurations and they are simple and small.
I saw that Moose defines
package: 'Moose-Hismo' with: [spec requires: 'Moose-Core'];
so may be this should be FAMIX-Core?
Or the extensions should be moved to another package but it will complexify the system.
I modified the moose configuration and the order looks better to me.
#('Moose-GenericImporter-Nicolasanquetil.47.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Moose-GenericImporter' )
#('Famix-Core-TudorGirba.222.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Famix-Core' )
#('Famix-SourceAnchor-TudorGirba.38.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Famix-SourceAnchor' )
#('Moose-Hismo-JurajKubelka.69.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Moose-Hismo' )
#('Famix-File-NicolasAnquetil.40.mcz' 'http://www.smalltalkhub.com/mc/Moose/Moose/main/' 'Famix-File' )
#('Famix-Java-TudorGirba.74.mcz' 'http://w
Problem 2
--------------
Now I found another problem
Algo-Clustering
MalArrayVector MalVectorDecorator MalSymetricMatrix MalVector
arrives before
LinearAlgebra
package: 'Moose-Algos-Clustering' ;
package: 'Moose-Algos-LinearAlgebra';
So I moved package: 'Moose-Algos-LinearAlgebra'; before
and I added a dependency
package: 'Moose-Algos-Clustering' with: [spec requires: 'Moose-Algos-LinearAlgebra'] ;
Of course the feedback loop is quite long….
So testing until the next problem. I think that we should build a tool that check dependencies.
could you change this information or do I do it?
Stef
10 years, 1 month
Build failed in Jenkins: moose-latest-dev-4.8 #887
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/887/>
------------------------------------------
Started by upstream project "gtoolkit" build number 253
originally caused by:
[URLTrigger] A change within the response URL invocation (log)
Building remotely on moose-ubuntu1204-dualproc-i386 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/hudson8606449502973630000.sh
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
+ bash
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.8
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./pharo 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[31m==== Startup Error: Error: Could not load Moose-TestResources-PackageBlueprint-P1-NicolasAnquetil.2.mcz: ConnectionTimedOut: Data receive timed out.
[0mMCHttpRepository(Object)>>error:
MCHttpRepository>>readStreamForFileNamed:do: in Block: [:exception | self error: 'Could not load ' , aStr...etc...
BlockClosure>>cull:
MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
ConnectionTimedOut(Exception)>>pass
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...
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:
[0m[31mGot startup errors:
[0m[31m Error: Could not load Moose-TestResources-PackageBlueprint-P1-NicolasAnquetil.2.mcz: ConnectionTimedOut: Data receive timed out.
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
10 years, 1 month
thanks for the new configuration
by Stéphane Ducasse
I will try when the jenkins buils decide to see the new moose version….
And I do not have the rigth accesses :(
Stef
10 years, 1 month
Missing change in latest Moose
by Stéphane Ducasse
MooseAlgos-Clustering is depending on MalArrayVector
so I suggested to do
spec
package: 'Moose-Algos-Graph' ;
package: 'Moose-Algos-LinearAlgebra';
package: 'Moose-Tests-Algos-Graph' ;
package: 'Moose-Algos-HierarchicalGraph' with: [spec requires: 'Moose-Algos-Graph'];
package: 'Moose-Tests-Algos-HierarchicalGraph' ;
package: 'Moose-Tests-Algos-LinearAlgebra' ;
package: 'Moose-Tests-Algos-Clustering' ;
package: 'Moose-Tests-Algos-InformationRetrieval' ;
package: 'Moose-Tests-Algos-FormalConceptAnalysis';
package: 'Moose-Tests-Algos-Lattice';
package: 'Moose-Algos-Clustering' with: [spec requires: 'Moose-Algos-LinearAlgebra'] ;
package: 'Moose-Algos-FormalConceptAnalysis';
package: 'Moose-Algos-Lattice';
package: 'Moose-Algos-InformationRetrieval';
package: 'Moose-Algos-Kontractor';
package: 'Moose-Tests-Algos-Kontractor' ;
should I commit this changes?
> Problem 2
> --------------
> Now I found another problem
>
> Algo-Clustering
>
> MalArrayVector MalVectorDecorator MalSymetricMatrix MalVector
> arrives before
> LinearAlgebra
>
>
> package: 'Moose-Algos-Clustering' ;
> package: 'Moose-Algos-LinearAlgebra';
>
> So I moved package: 'Moose-Algos-LinearAlgebra'; before
> and I added a dependency
>
>
> package: 'Moose-Algos-Clustering' with: [spec requires: 'Moose-Algos-LinearAlgebra'] ;
>
>
> Of course the feedback loop is quite long….
> So testing until the next problem. I think that we should build a tool that check dependencies.
>
> could you change this information or do I do it?
>
>
> Stef
10 years, 1 month
