July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Downloading 1.4

by StÃ©phane Ducasse

Strange because I run 1.4 on 4.2.5beta1U, 5.7b3, 5.7.4 Stef On Jul 26, 2011, at 7:53 PM, Sean P. DeNigris wrote: > > StÃ©phane Ducasse wrote: >> >> https://ci.lille.inria.fr/pharo/job/ >> > > Thanks. It doesn't seem to launch with the Mac Carbon 4.2.5 VM (the only one > with all the plugins built :( ), although it did launch with the Stack > 4.0.0. > > I created Issue 4553. > > -- > View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696515.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Igor Stasenko

On 26 July 2011 20:12, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote: >> >> We should fix the VMs. >> > > Yes, I've reported several missing plugins to the VM issue tracker, but the > noble maintainers are overworked ( and underpaid :) ). For now, anyone using > the ObjectiveC, Quicktime, or Applescript plugins (missing at the time I > reported them) will not be able to upgrade to 1.4. > If i'm not mistaken, recently Esteban added ObjectiveC plugin into Cocoa builds. https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog-Mac-Cocoa/changes > Sean > > -- > View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696591.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Sean P. DeNigris

4.2.5 (interpreter) -- View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696602.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Igor Stasenko

What is the version of VM you refer to? Because here the VM i downloaded from Hudson (a Carbon one) and it opens an image without problem: Smalltalk vmVersion 'Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-IgorStasenko.108] CogVM VM 4.0.0 https://git.gitorious.org/cogvm/blessed.git Commit: fde60cf1a440cd0ba4c56470dffff4aafc664d88 Date: Fri Jul 22 14:16:11 2011 +0200 By: Igor Stasenko <siguctua(a)gmail.com>' Pharo1.4a Latest update: #14060 On 26 July 2011 20:04, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jul 26, 2011, at 7:58 PM, Sean P. DeNigris wrote: > >> >> Marcus Denker-4 wrote: >>> >>> Is it really realistic to support 20 differents VMs? Who is going to test? >>> >> >> I'm sure that once the new VMs stabilize, it will not be an issue, but given >> that the Stack/Cog VMs do not have all the plugins, what do you suggest for >> right now? > > We should fix the VMs. > > We can *not* support to run on all old VMs. > > Â Â Â Â Marcus > > -- > Marcus Denker > Do it together: http://taskfor.us > > > -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Sean P. DeNigris

Marcus Denker-4 wrote: > > We should fix the VMs. > Yes, I've reported several missing plugins to the VM issue tracker, but the noble maintainers are overworked ( and underpaid :) ). For now, anyone using the ObjectiveC, Quicktime, or Applescript plugins (missing at the time I reported them) will not be able to upgrade to 1.4. Sean -- View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696591.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 26, 2011

Re: [Pharo-project] TestCase>>#should:notTakeMoreThan: behaves not well in headless mode

by Igor Stasenko

On 26 July 2011 20:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > may be I'm wrong but should:notTakeMoreThan: does not tell me that it is forking a process. > So I would prefer it does not. > It forks a process, because if code under the question takes forever to evaluate, you cannot stop it unless using another process who watching over it. evaluationProcess := [ result := aBlock value. evaluated := true. delay unschedule. testProcess resume ] forkNamed: 'Process to evaluate should: notTakeMoreThanMilliseconds:'. > > On Jul 26, 2011, at 7:06 PM, Igor Stasenko wrote: > >> It forks a process for evaluating a block you passing. >> And it works quite well if there's no exception during block evaluation.. >> but if there is, then it signals the TestFailure exception, not in a >> process who waits test to be finished, >> but in a process which forked. >> And then since there is no exception handler, it using default action, >> which just to open a debugger. >> In headless mode it leads to immediate quit from image and logging >> error report. >> >> Like following: >> >> THERE_BE_DRAGONS_HERE >> MessageNotUnderstood: >> NonInteractiveUIManager>>openDebuggerOn:context:label:contents:fullView: >> 26 July 2011 6:35:08 pm >> >> VM: unix - i686 - linux-gnu - Croquet Closure Cog VM [CoInterpreter >> VMMaker-oscog-IgorStasenko.108] >> Image: Pharo1.4a [Latest update: #14025] >> >> NonInteractiveUIManager(Object)>>doesNotUnderstand: >> #openDebuggerOn:context:label:contents:fullView: >> Â Â Â Receiver: a NonInteractiveUIManager >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â aMessage: Â Â Â openDebuggerOn: a Process in nil context: >> MethodContextTest(TestCase)...etc... >> Â Â Â Â Â Â Â exception: Â Â Â MessageNotUnderstood: >> NonInteractiveUIManager>>openDebuggerOn:contex...etc... >> Â Â Â Â Â Â Â resumeValue: Â Â nil >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â uiManager: Â Â Â a MorphicUIManager >> Â Â Â Â Â Â Â doNotQuitOnRestart: Â Â false >> >> >> Debugger class>>openOn:context:label:contents:fullView: >> Â Â Â Receiver: Debugger >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â process: Â Â Â Â a Process in nil >> Â Â Â Â Â Â Â context: Â Â Â Â MethodContextTest(TestCase)>>signalFailure: >> Â Â Â Â Â Â Â title: Â 'TestFailure: Assertion failed' >> Â Â Â Â Â Â Â contentsStringOrNil: Â Â nil >> Â Â Â Â Â Â Â bool: Â false >> Â Â Â Â Â Â Â fullView: Â Â Â false >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â superclass: Â Â CodeHolder >> Â Â Â Â Â Â Â methodDict: Â Â a >> MethodDictionary(#addOptionalButtonsTo:at:plus:->(Debugger>>#addO...etc... >> Â Â Â Â Â Â Â format: Â Â Â Â 168 >> Â Â Â Â Â Â Â instanceVariables: Â Â Â #('interruptedProcess' 'interruptedController' >> 'contextStack...etc... >> Â Â Â Â Â Â Â organization: Â ('*Polymorph-Widgets' addOptionalButtonsTo:at:plus: >> buildMorphicN...etc... >> Â Â Â Â Â Â Â subclasses: Â Â nil >> Â Â Â Â Â Â Â name: Â #Debugger >> Â Â Â Â Â Â Â classPool: Â Â Â a Dictionary(#AlwaysOpenFullDebugger->false >> #ContextStackKeystrokes-...etc... >> Â Â Â Â Â Â Â sharedPools: Â Â nil >> Â Â Â Â Â Â Â environment: Â Â a SystemDictionary(lots of globals) >> Â Â Â Â Â Â Â category: Â Â Â #'Tools-Debugger' >> Â Â Â Â Â Â Â traitComposition: Â Â Â {} >> Â Â Â Â Â Â Â localSelectors: Â Â Â Â nil >> >> >> [:tool | ^ tool >> Â Â Â Â Â Â Â openOn: aProcess >> Â Â Â Â Â Â Â context: aContext >> Â Â Â Â Â Â Â label: aString >> Â Â Â Â Â Â Â contents: contents >> Â Â Â Â Â Â Â fullView: aBool] in ToolRegistry>>debug:context:label:contents:fullView: >> Â Â Â Receiver: a ToolRegistry >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â aProcess: Â Â Â Debugger >> Â Â Â Â Â Â Â aContext: Â Â Â a Process in nil >> Â Â Â Â Â Â Â aString: Â Â Â Â MethodContextTest(TestCase)>>signalFailure: >> Â Â Â Â Â Â Â contents: Â Â Â 'TestFailure: Assertion failed' >> Â Â Â Â Â Â Â aBool: Â nil >> Â Â Â Â Â Â Â tool: Â false >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â tools: Â an IdentityDictionary(#basicInspector->BasicInspector >> #browser->[self de...etc... >> Â Â Â Â Â Â Â inspectorsMap: Â an >> IdentityDictionary(#CompiledMethod->#CompiledMethodInspector ...etc... >> >> >> ToolRegistry>>using:do: >> Â Â Â Receiver: a ToolRegistry >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â aToolName: Â Â Â #debugger >> Â Â Â Â Â Â Â aBlock: Â Â Â Â [:tool | ^ tool >> Â Â Â Â Â Â Â openOn: aProcess >> Â Â Â Â Â Â Â context: aContext >> Â Â Â Â Â Â Â label: aString...etc... >> Â Â Â Â Â Â Â tool: Â Debugger >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â tools: Â an IdentityDictionary(#basicInspector->BasicInspector >> #browser->[self de...etc... >> Â Â Â Â Â Â Â inspectorsMap: Â an >> IdentityDictionary(#CompiledMethod->#CompiledMethodInspector ...etc... >> >> >> ToolRegistry>>debug:context:label:contents:fullView: >> Â Â Â Receiver: a ToolRegistry >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â aProcess: Â Â Â a Process in nil >> Â Â Â Â Â Â Â aContext: Â Â Â MethodContextTest(TestCase)>>signalFailure: >> Â Â Â Â Â Â Â aString: Â Â Â Â 'TestFailure: Assertion failed' >> Â Â Â Â Â Â Â contents: Â Â Â nil >> Â Â Â Â Â Â Â aBool: Â false >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â tools: Â an IdentityDictionary(#basicInspector->BasicInspector >> #browser->[self de...etc... >> Â Â Â Â Â Â Â inspectorsMap: Â an >> IdentityDictionary(#CompiledMethod->#CompiledMethodInspector ...etc... >> >> >> Process>>debug:title:full: >> Â Â Â Receiver: a Process in nil >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â context: Â Â Â Â MethodContextTest(TestCase)>>signalFailure: >> Â Â Â Â Â Â Â title: Â 'TestFailure: Assertion failed' >> Â Â Â Â Â Â Â bool: Â false >> Â Â Â Â Â Â Â topCtxt: Â Â Â Â Process>>debug:title:full: >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â nextLink: Â Â Â nil >> Â Â Â Â Â Â Â suspendedContext: Â Â Â nil >> Â Â Â Â Â Â Â priority: Â Â Â 40 >> Â Â Â Â Â Â Â myList: Â Â Â Â nil >> Â Â Â Â Â Â Â threadId: Â Â Â nil >> Â Â Â Â Â Â Â errorHandler: Â nil >> Â Â Â Â Â Â Â name: Â 'Process to evaluate should: notTakeMoreThanMilliseconds:' >> Â Â Â Â Â Â Â env: Â Â nil >> >> >> Process>>debug:title: >> Â Â Â Receiver: a Process in nil >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â context: Â Â Â Â MethodContextTest(TestCase)>>signalFailure: >> Â Â Â Â Â Â Â title: Â 'TestFailure: Assertion failed' >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â nextLink: Â Â Â nil >> Â Â Â Â Â Â Â suspendedContext: Â Â Â nil >> Â Â Â Â Â Â Â priority: Â Â Â 40 >> Â Â Â Â Â Â Â myList: Â Â Â Â nil >> Â Â Â Â Â Â Â threadId: Â Â Â nil >> Â Â Â Â Â Â Â errorHandler: Â nil >> Â Â Â Â Â Â Â name: Â 'Process to evaluate should: notTakeMoreThanMilliseconds:' >> Â Â Â Â Â Â Â env: Â Â nil >> >> >> TestFailure>>defaultAction >> Â Â Â Receiver: TestFailure: Assertion failed >> Â Â Â Arguments and temporary variables: >> >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â messageText: Â Â 'Assertion failed' >> Â Â Â Â Â Â Â tag: Â Â nil >> Â Â Â Â Â Â Â signaler: Â Â Â MethodContextTest>>#testClosureRestart >> Â Â Â Â Â Â Â signalContext: Â TestFailure(Exception)>>signal >> Â Â Â Â Â Â Â handlerContext: Â Â Â Â nil >> Â Â Â Â Â Â Â outerContext: Â nil >> >> .... >> >> >> This happens when you run a >> MethodContextTest>>#testClosureRestart >> on Cog VM. >> >> Why it fails is another story :) >> But we need to fix the tester somehow, in order to continue running >> rest of tests instead of quitting to OS. >> >> The problem is that "aBlock value" which signals the exception should >> be wrapped by exception handler. >> And then #should:notTakeMoreThan: should report that exception to the >> main process which runs the test. >> So, a failure would be either due to timeout or due to failing running >> the code without exceptions. >> >> Any suggestions? >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Marcus Denker

On Jul 26, 2011, at 7:58 PM, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote: >> >> Is it really realistic to support 20 differents VMs? Who is going to test? >> > > I'm sure that once the new VMs stabilize, it will not be an issue, but given > that the Stack/Cog VMs do not have all the plugins, what do you suggest for > right now? We should fix the VMs. We can *not* support to run on all old VMs. Marcus -- Marcus Denker Do it together: http://taskfor.us

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Sean P. DeNigris

Marcus Denker-4 wrote: > > Is it really realistic to support 20 differents VMs? Who is going to test? > I'm sure that once the new VMs stabilize, it will not be an issue, but given that the Stack/Cog VMs do not have all the plugins, what do you suggest for right now? Sean -- View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696542.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Marcus Denker

On Jul 26, 2011, at 7:53 PM, Sean P. DeNigris wrote: > > StÃ©phane Ducasse wrote: >> >> https://ci.lille.inria.fr/pharo/job/ >> > > Thanks. It doesn't seem to launch with the Mac Carbon 4.2.5 VM (the only one > with all the plugins built :( ), although it did launch with the Stack > 4.0.0. > > I created Issue 4553. Is it really realistic to support 20 differents VMs? Who is going to test? Marcus -- Marcus Denker Do it together: http://taskfor.us

July 26, 2011

Re: [Pharo-project] Downloading 1.4

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > https://ci.lille.inria.fr/pharo/job/ > Thanks. It doesn't seem to launch with the Mac Carbon 4.2.5 VM (the only one with all the plugins built :( ), although it did launch with the Stack 4.0.0. I created Issue 4553. -- View this message in context: http://forum.world.st/Downloading-1-4-tp3696454p3696515.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 26, 2011