Moose-dev July 2013

moose-dev@list.inf.unibe.ch

28 participants
130 discussions

Issue 958 in moose-technology: parameterizableClass does not have an opposite

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix New issue 958 by tu...(a)tudorgirba.com: parameterizableClass does not have an opposite http://code.google.com/p/moose-technology/issues/detail?id=958 parameterizableClass <MSEProperty: #parameterizableClass type: #FAMIXParameterizableClass> <MSEComment: 'Base type of this parameterized type.'> ^self privateState attributeAt: #parameterizableClass ifAbsent: [nil] We should get an opposite to a newly created FAMIXParameterizableClass>>#parameterizedTypes -- 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, 4 months

Issue 959 in moose-technology: clientClasses and providerClasses should be renamed to clientTypes and providerTypes

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.8 New issue 959 by tu...(a)tudorgirba.com: clientClasses and providerClasses should be renamed to clientTypes and providerTypes http://code.google.com/p/moose-technology/issues/detail?id=959 These methods actually return types, like for example in: clientClasses <MSEProperty: #clientClasses type: #FAMIXType> <multivalued> <derived> <MSEComment: 'returns a set of all the classes that depend on the receiver'> ^ self queryAllIncomingAssociations atTypeScope withoutSelfLoops Thus, we should deprecate clientClasses and renamed it to clientTypes -- 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, 4 months

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/760/> ------------------------------------------ Started by timer Started by upstream project "fame" build number 130 originally caused by: Started by timer Started by upstream project "gtoolkit" build number 202 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/hudson457599445756841378.sh + wget --quiet -O - http://get.pharo.org/20+vm + 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/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 [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>>connectTo:port:waitForConnectionFor: in Block: [ConnectionTimedOut signal: 'Cannot connect to '... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Data receive timed out. [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 4 months

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/758/> ------------------------------------------ Started by upstream project "glamour" build number 202 originally caused by: Started by timer Started by upstream project "petitjava" build number 150 originally caused by: Started by timer Started by upstream project "petitparser" build number 147 originally caused by: Started by timer Started by upstream project "roassal" build number 346 originally caused by: Started by timer Building remotely on moose-slave 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/hudson2810844350764825185.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[31m==== Startup Error: Error: Could not resolve: Collections-Support [Collections-Support] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://smalltalkhub.com/mc/Pharo/XMLWriter/main ERROR: 'GoferRepositoryError: Could not access http://ss3.gemtalksystems.com/ss/Pharo20: ZnHttpUnsuccessful: 500 Internal Server Error' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: Collections-Support [Collections-Support] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://smalltalkhub.com/mc/Pharo/XMLWriter/main ERROR: 'GoferRepositoryError: Could not access http://ss3.gemtalksystems.com/ss/Pharo20: ZnHttpUnsuccessful: 500 Internal Server Error' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 4 months

Re: what about a mooseday at Lille in fall?

by Stephan Eggermont

Sounds like a good idea. Stephan

11 years, 4 months

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/751/> ------------------------------------------ [...truncated 520 lines...] bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: @ @ basicNew truncated truncated @ truncated truncated @ basicNew @ @ basicNew @ @ basicNew @ @ @ perform:with: @ @ perform:with: @ basicNew @ @ basicNew basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: basicAt: bitShiftMagnitude: basicAt: bitAnd: bitShiftMagnitude: basicAt: + bitOr: digitCompare: bitShiftMagnitude: perform:with: @ @ basicNew truncated truncated @ truncated truncated @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew class basicNew @ basicNew basicNew: stack page bytes 4096 available headroom 3300 minimum unused headroom 3476 (last object overwritten) ./pharo: line 11: 14073 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -nodisplay "$@" Build 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/Mondrian-Tests-Test.x…> 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 581 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Mondrian-Tests-Test.x…> : 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/Mondrian-Tests-Test.x…;> lineNumber: 581; 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, 5 months

Re: [Pharo-users] Re: [ann] snapshotcello

by Tudor Girba

Hi, On Jul 23, 2013, at 11:51 PM, "Dale K. Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > Stef, > > I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). What is not clear? I would be interested in describing our scenario in more details because I think this is a development pattern. But, I need some concrete questions to start from. > However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. I still do not understand why Versionner would be affected by the current versions given that we are only generating versions that should be immutable hence no need for management. > With that said it _is_ performing a useful function ... > > I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... Having a different way to store the information should be no problem. I am curious about your ideas. Cheers, Doru > Dale > > [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html > ----- Original Message ----- > | From: "Stéphane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> > | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" > | <pharo-dev(a)lists.pharo.org> > | Sent: Tuesday, July 23, 2013 2:17:50 PM > | Subject: [Moose-dev] Re: [ann] snapshotcello > | > | Nice to see SnapshotCello coming to live. May be it should be > | integrated to Metacello. > | Because everybody may need this cool feature. > | > | Stef > | > | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> > | wrote: > | > | > Hi, > | > > | > Stef and I developed Snapshotcello, a little utility that enables > | > you to freeze a snapshot of a given configuration based on what is > | > already loaded in your current image. > | > > | > The idea is simple. You develop against the latest versions of all > | > packages, and commit your changes for each package. When you are > | > ready for a release, you assemble your image, and generate a > | > snapshot version that can be reloaded later. > | > > | > Here is an example of how it can work to take a snapshot of a > | > development version: > | > Snapshotcello new > | > configurationClass: ConfigurationOfMoose; > | > configurationVersion: #development; > | > publishVersion: '4.8-snapshot' > | > > | > You can find more details here: > | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > | > > | > You can get the code at: > | > Gofer new > | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > | > package: 'ConfigurationOfSnapshotcello'; > | > load. > | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) > | > loadDevelopment > | > > | > Cheers, > | > Doru > | > > | > -- > | > www.tudorgirba.com > | > > | > "Every successful trip needs a suitable vehicle." > | > > | > > | > > | > > | > > | > _______________________________________________ > | > Moose-dev mailing list > | > Moose-dev(a)iam.unibe.ch > | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > | > | _______________________________________________ > | Moose-dev mailing list > | Moose-dev(a)iam.unibe.ch > | https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > -- www.tudorgirba.com "Live like you mean it."

11 years, 5 months

Re: [Pharo-dev] Re: [ann] snapshotcello

by Stéphane Ducasse

On Jul 23, 2013, at 11:51 PM, Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Stef, > > I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). > > However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. Indeed. May be in the future we could recreate a simple compliant spec driven method by interpreting the existing configuration trees but this requires some work. > > With that said it _is_ performing a useful function ... > > I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... > > Dale > > [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html > ----- Original Message ----- > | From: "Stéphane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> > | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" > | <pharo-dev(a)lists.pharo.org> > | Sent: Tuesday, July 23, 2013 2:17:50 PM > | Subject: [Moose-dev] Re: [ann] snapshotcello > | > | Nice to see SnapshotCello coming to live. May be it should be > | integrated to Metacello. > | Because everybody may need this cool feature. > | > | Stef > | > | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> > | wrote: > | > | > Hi, > | > > | > Stef and I developed Snapshotcello, a little utility that enables > | > you to freeze a snapshot of a given configuration based on what is > | > already loaded in your current image. > | > > | > The idea is simple. You develop against the latest versions of all > | > packages, and commit your changes for each package. When you are > | > ready for a release, you assemble your image, and generate a > | > snapshot version that can be reloaded later. > | > > | > Here is an example of how it can work to take a snapshot of a > | > development version: > | > Snapshotcello new > | > configurationClass: ConfigurationOfMoose; > | > configurationVersion: #development; > | > publishVersion: '4.8-snapshot' > | > > | > You can find more details here: > | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > | > > | > You can get the code at: > | > Gofer new > | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > | > package: 'ConfigurationOfSnapshotcello'; > | > load. > | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) > | > loadDevelopment > | > > | > Cheers, > | > Doru > | > > | > -- > | > www.tudorgirba.com > | > > | > "Every successful trip needs a suitable vehicle." > | > > | > > | > > | > > | > > | > _______________________________________________ > | > Moose-dev mailing list > | > Moose-dev(a)iam.unibe.ch > | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > | > | _______________________________________________ > | Moose-dev mailing list > | Moose-dev(a)iam.unibe.ch > | https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | >

11 years, 5 months

Is the Moose Book available as PDF?

by MartinW

Hi, is there a way to get the Moose Book as a PDF? That would be very handy. M. -- View this message in context: http://forum.world.st/Is-the-Moose-Book-available-as-PDF-tp4700309.html Sent from the Moose mailing list archive at Nabble.com.

11 years, 5 months

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/747/> ------------------------------------------ [...truncated 545 lines...] perform:with: @ basicNew class copyBits basicNew new: shallowCopy shallowCopy shallowCopy shallowCopy basicNew new: @ @ basicNew @ shallowCopy basicNew @ @ basicNew @ @ basicNew basicNew @ @ basicNew perform:with: perform:with: @ basicNew class stringHash:initialHash: class stringHash:initialHash: basicNew at:put: basicNew class stringHash:initialHash: class class class class class stringHash:initialHash: class class class class basicNew at:put: basicNew class stringHash:initialHash: class class class class class class class stringHash:initialHash: class class class class class class basicNew at:put: new: class stringHash:initialHash: at:put: class stringHash:initialHash: at:put: class stringHash:initialHash: at:put: class stringHash:initialHash: at:put: class stringHash:initialHash: class class at:put: basicNew class stringHash:initialHash: class stringHash:initialHash: basicNew at:put: @ @ basicNew class copyBits @ perform:with: @ @ perform:with: @ basicNew class copyBits basicNew new: shallowCopy shallowCopy shallowCopy shallowCopy basicNew new: @ @ basicNew @ shallowCopy basicNew @ @ basicNew @ @ basicNew basicNew @ @ basicNew perform:with: perform:with: @ basicNew class stringHash:initialHash: class stringHash:initialHash: basicNew at:put: basicNew class stringHash:initialHash: class class class class class stringHash:initialHash: class class class class basicNew at:put: basicNew class stringHash:initialHash: class class class class class class class stringHash:initialHash: class class class class class class basicNew at:put: new: stack page bytes 4096 available headroom 3300 minimum unused headroom 3464 (last object overwritten) ./pharo: line 11: 12978 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -nodisplay "$@" Build 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/Mondrian-Tests-Test.x…> 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 485 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Mondrian-Tests-Test.x…> : 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/Mondrian-Tests-Test.x…;> lineNumber: 485; 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, 5 months

← Newer
1
...
4
5
6
7
8
9
10
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2013