Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: Performance profiling of PetitDelphi

by Stephan Eggermont

Thanks Doru. Hmm, you might want to avoid pasting a 1MB text into the sample area of PetitParser browser. 100% cpu and uninterruptable for quite some time now. Stephan

11 years, 10 months

Performance profiling of PetitDelphi

by Stephan Eggermont

5 minutes for parsing 8MB is not very good, especially for people used to Delphi compilation speed. Any hints on how to profile the PDDelphiParser? I'm sure there are lots of very inefficient productions. Just counting method sends? Cheers, Stephan

11 years, 10 months

Issue 931 in moose-technology: Moose Meta Browser - type and opposite values clipped on left

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 931 by alan.mcn...(a)gmail.com: Moose Meta Browser - type and opposite values clipped on left http://code.google.com/p/moose-technology/issues/detail?id=931 On selecing an Entity in the top left panel of the Moose Meta Browser, the Relation name/type/opposite are displayed. While the name is well displayed, the display of the type and opposite values are clipped on the left, and part of the first character cannot be seen. Similarly, if Property tab is selected, the type values are similarly clipped. -- 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

11 years, 10 months

Issue 934 in moose-technology: Moose Meta Browser - Entities panel not updated when selecting Entity in Map

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 934 by alan.mcn...(a)gmail.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934 In the Map panel it is possible to select a box representing an Entity. When this is done, the Entity and its relationships are highlighted in red in the Map pane. Also, the Relations / Properties and Comments panes are updated with information for that Entity shown. However, the Entity pane is NOT updated. I would expect that the Entities pane would be changed so that the Entity selected in the Map pane would also be selected in the Entities pane, including expanding any Entity hierarchy as required. -- 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

11 years, 10 months

Re: PetitDelphi status update

by Stephan Eggermont

Hmm, forum.world.st seems to have lost a mail. http://moose-dev.97923.n3.nabble.com/PetitDelphi-status-update-td4027969.ht… Stephan

11 years, 10 months

Issue 947 in moose-technology: TextPresentations should support setting the selectionInterval on creation

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 947 by chisvasi...(a)gmail.com: TextPresentations should support setting the selectionInterval on creation http://code.google.com/p/moose-technology/issues/detail?id=947 When creating a text presentation the user should be able to specify a selectionInterval: GLMTextPresentation new selectionIntervalBlock: [ ... ] -- 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

11 years, 10 months

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/610/> ------------------------------------------ Started by upstream project "petitjava" build number 96 originally caused by: Started by timer Started by upstream project "petitparser" build number 112 originally caused by: Started by timer Started by upstream project "roassal" build number 290 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/hudson1442340997866419567.sh + bash + wget --quiet -O - http://get.pharo.org/20+vm 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/stable.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 Please install the 32bit libraries sudo aptitude install ia32-libs + ./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 137 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)>>hResizeScrollBar PaginatedMorphTreeMorph>>hResizeScrollBar PaginatedMorphTreeMorph(ScrollPane)>>resizeScrollBars PaginatedMorphTreeMorph(ScrollPane)>>hideOrShowScrollBars 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: [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-Morphic…> 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-Morphic…> : 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-Morphic…;> 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

11 years, 10 months

Issue 943 in moose-technology: Integrate Rubric in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 943 by tu...(a)tudorgirba.com: Integrate Rubric in Glamour http://code.google.com/p/moose-technology/issues/detail?id=943 Rubric can be found at: Gofer new url: 'http://www.smalltalkhub.com/mc/AlainPlantec/Rubric/main'; package: 'Rubric'; load. In particular, we should integrate RubScrolledTextMorph and RubTextFieldMorph. -- 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

11 years, 10 months

an stable Moose version for pharo2 ?

by Guillermo Polito

Hi guys, I was building a simple CI job to run an acceptance test for the pharovm. Now, as we talked with Esteban and Camillo, we want to: - take an stable pharo20 - load an stable freezed version of moose - load an stable freezed version of seaside - run tests as a first attempt. However, I find the configuration of moose has no 4.8 version as I was expecting, and loading the latest development version does not really do it (we want to test the vm, not moose :). How can I get a freezed version of moose working on 2.0? Tx!! Guille

11 years, 10 months

moose 4.8

by Tudor Girba

Hi, As soon as all tests are green, we will release 4.8. The target would be end of next week at the latest. Afterwards, we move to Moose 5.0 on top of Pharo 3.0. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev