Speed up of Mondrian
by Alexandre Bergel
Hi!
I've just integrated the fix of Mathieu.
1.395 : Integrated optimization from Mathieu. Excellent job!
[| view |
view := ROMondrianViewBuilder new.
view nodes: Object withAllSubclasses.
view edgesFrom: #superclass.
view treeLayout.
view applyLayout ] timeToRun
=> 91856 before this version
=> 48519 with this version
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
9 years, 9 months
is the loadDirective really working?
by Stéphane Ducasse
Hi dale
I do not understand because
when I do
(ConfigurationOfMoose project version: #development) record loadDirective
-> I get an error telling that 1.3 of Shout is not found
then if I run
(ConfigurationOfMondrian project version: #development) record loadDirective
I get another errror
and if I try again
(ConfigurationOfMoose project version: #development) record loadDirective
-> I get anANOTHER error about 1.1.7 of XML support.
So I'm totally puzzled.
Stef
9 years, 9 months
Collections-String dirty
by Stéphane Ducasse
Hi
what do we do with the latest moose which has dirty packages and
- remove trim* from strings
- remove MessageSend value: value:value:
- asMorph
It seems that this is due to the fact that Magritte uses Grease and that grease has trim as its own extensions.
So we should fix Magritte30 configuration to handle that.
I can have a look with esteban this afternoon.
Stef
9 years, 9 months
Snapshotcello class comments?
by Stéphane Ducasse
Hi doru
I followed the class comments and I tried
Snapshotcello new
configurationClass: ConfigurationOfFourDBrowser;
sourceVersion: #development;
newVersion: '1.0-snapshot-FakeDeliveryAugust2013';
snapshot;
makeStableFor: #'pharo2.x'
and the system barks because newVersion: is not found.
I'm checking.
Stef
9 years, 9 months
Build failed in Jenkins: moose-latest-dev-4.8 #824
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/824/>
------------------------------------------
Started by upstream project "roassal" build number 361
originally caused by:
[URLTrigger] A change within the response URL invocation (log)
Started by upstream project "roassal" build number 362
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/hudson8478967190305127199.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+ ./pharo moose-latest-dev-4.8.image mooseimagesetup
+ ./pharo moose-latest-dev-4.8.image moosetest --junit-xml-output
[31m[33m
===============================================================================
Notice: Running tests in 136 Packages
===============================================================================
[0m[0m[31mMessageNotUnderstood: receiver of "hasPositiveExtent" is nil
[0mUndefinedObject(Object)>>doesNotUnderstand: #hasPositiveExtent
ScrollBar(Morph)>>invalidRect:from:
ScrollBar(Morph)>>invalidRect:
ScrollBar(Morph)>>position:
ScrollBar(Morph)>>bounds:
PaginatedMorphTreeMorph(ScrollPane)>>vResizeScrollBar
PaginatedMorphTreeMorph(ScrollPane)>>resizeScrollBars
PaginatedMorphTreeMorph(ScrollPane)>>extent:
PaginatedMorphTreeMorph(MorphTreeMorph)>>extent:
PaginatedMorphTreeMorph>>extent:
PaginatedMorphTreeMorph(Morph)>>bounds:
PaginatedMorphTreeMorph(Morph)>>layoutInBounds:
PaginatedMorphTreeMorph(Morph)>>layoutProportionallyIn:
ProportionalLayout>>layout:in: in Block: [:m | m layoutProportionallyIn: newBounds]
Array(SequenceableCollection)>>do:
PanelMorph(Morph)>>submorphsDo:
ProportionalLayout>>layout:in:
PanelMorph(Morph)>>doLayoutIn:
PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds]
BlockClosure>>on:do:
PanelMorph(Morph)>>fullBounds
PanelMorph(Morph)>>submorphBounds in Block: [:m | | subBox | m visible...
Array(SequenceableCollection)>>do:
PanelMorph(Morph)>>submorphBounds
PanelMorph(Morph)>>privateFullBounds
PanelMorph(Morph)>>doLayoutIn:
PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds]
BlockClosure>>on:do:
PanelMorph(Morph)>>fullBounds
LazyTabGroupMorph(Morph)>>submorphBounds in Block: [:m | | subBox | m visible...
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed: <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> at hudson.remoting.Channel@2f17e8fb:moose-ubuntu1204-dualproc-i386
at hudson.FilePath.act(FilePath.java:848)
at hudson.FilePath.act(FilePath.java:825)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122)
at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732)
at hudson.model.Run.execute(Run.java:1568)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.util.IOException2: Failed to read <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morph...>
at hudson.tasks.junit.TestResult.parse(TestResult.java:244)
at hudson.tasks.junit.TestResult.parse(TestResult.java:163)
at hudson.tasks.junit.TestResult.parse(TestResult.java:140)
at hudson.tasks.junit.TestResult.<init>(TestResult.java:116)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: org.dom4j.DocumentException: Error on line 111 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morph...> : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity.
at org.dom4j.io.SAXReader.read(SAXReader.java:482)
at org.dom4j.io.SAXReader.read(SAXReader.java:264)
at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129)
at hudson.tasks.junit.TestResult.parse(TestResult.java:227)
... 15 more
Caused by: org.xml.sax.SAXParseException; systemId: file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morph...;> lineNumber: 111; columnNumber: 1; XML document structures must start and end within the same entity.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:391)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1404)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:882)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:582)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1370)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1740)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1393)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2769)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
at org.dom4j.io.SAXReader.read(SAXReader.java:465)
... 18 more
9 years, 9 months
Build failed in Jenkins: moose-latest-dev-4.8 #816
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/816/>
------------------------------------------
Started by upstream project "gtoolkit" build number 218
originally caused by:
[URLTrigger] A change within the response URL invocation (log)
Started by timer
Started by upstream project "fame" build number 144
originally caused by:
Started by timer
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/hudson2910957992351001345.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: 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
9 years, 9 months
clientBehaviours and providerBehaviours in FAMIXBehaviouralEntity
by Usman Bhatti
Hello,
There are some new methods introduced in FAMIXBehaviouralEntity:
clientBehaviours and providerBehaviours.
clientBehaviours
<MSEProperty: #clientBehaviours type: #FAMIXBehaviouralEntity>
<multivalued> <derived>
<MSEComment: 'All behaviours that depend on the receiver'>
^ self invokingMethods
InvokingMethods is defined in one of the subclasses of
FAMIXBehaviouralEntity: FAMIXMethod and not the other subclass,
FAMIXFunction. I have my code that subclasses FAMIXFunction and when I try
to export the object to an MSE, there is an error:
MyFunction(Object)>>doesNotUnderstand: #invokingMethods.
So, IMO, clientBehaviours and providerBehaviours methods need to point to a
method at the same level instead of sending message to a subclass method.
regards,
Usman
9 years, 9 months
Glamour: vertical action list presentation?
by Johan Fabry
Hi all,
I used to have a list of vertical buttons in the old version of AspectMaps (Moose 4.3), but now it appears that I cannot have these buttons vertically. I always get them horizontally, even if I add an isHorizontal: false, e.g. as in the code as below:
(aBrowser transmit)
to: #buttons; from: #models;
andShow: [ :a |
(a actionList) title: 'Structural Zoom';
isHorizontal: false;
populate: #selection on: $2 entitled: 'By Query'
with: (et cetera)
Is there a way to get my buttons stacked vertically? sending stackedVerticallyArrangement only works on the container of the buttons (the 'a' in the code above), not on the buttons themselves.
Thanks in advance,
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
9 years, 9 months
