March 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo 1.4 Tests-Unix vs. Pharo Kernel Reload Tests-Unix
by Pavel Krivanek March 15, 2012

March 15, 2012

Hi, good news. We have got the same amount of test failures in th job Pharo Kernel Reload Tests-Unix as in the job Pharo 1.4 Tests-Unix https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4%20Tests-Un… https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Relo… On the other had, they differ in one failing job. For the standard Pharo the test named Tests.Monticello.MCFileInTest.testStWriter is always failing but on reloaded Pharo this tests almost never fails (sometimes yes). For reloaded Pharo, the test named Tests.Monticello.MCStWriterTest.testMethodDefinitionWithBangs is failing. The reason is in empty string when you get some timeStamps: (MCStWriterTest >> #methodWithBangs) timeStamp. When I load the Tests package again, it works well. -- Pavel

1 0

[Pharo-project] Pharo Kernel Reload Tests-Unix - Build # 8 - Still unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 15, 2012

March 15, 2012

1 0

[Pharo-project] Three presentations at Dyncon 2012 in Stockholm
by GÃ¶ran Krampe March 15, 2012

March 15, 2012

Hey fellas! Just wanted to mention that Smalltalk and Amber in particular has a fairly strong presence this year at Dyncon 2012 (http://swdc.se/dyncon2012/) - I am presenting "Brave new world" (the architecture of SmalltalkHub, which includes Amber, Phriak, Pharo, Seaside-REST etc) (see http://swdc.se/dyncon2012/sessions/) - Nicolas is presenting Amber. - Jason Ayers is probably presenting something Smalltalk related :) regards, GÃ¶ran

1 0

[Pharo-project] Something is wrong with the CI server
by Pavel Krivanek March 15, 2012

March 15, 2012

Hi, is CI server working well? Jobs seem to be at least two times slower and some were running over whole night. I see no problem with the 1.4 image nor VM. -- Pavel

1 0

[Pharo-project] [update 1.4] #14392
by Marcus Denker March 15, 2012

March 15, 2012

14392 ----- Issue 5482: Class copy is broken http://code.google.com/p/pharo/issues/detail?id=5482 Issue 5454: CombinedChar initialization http://code.google.com/p/pharo/issues/detail?id=5454 Issue 4187: ByteTextConverters subclasses tables need to be checked (a.o. ISO88592TextConverter) http://code.google.com/p/pharo/issues/detail?id=4187 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] [squeak-dev] Simulation discrepancy with #return:
by Eliot Miranda March 15, 2012

March 15, 2012

Hi Yoshiki, Hi Hans-Martin, Hi All, On Tue, Mar 13, 2012 at 10:25 AM, Yoshiki Ohshima <Yoshiki.Ohshima(a)acm.org>wrote: > At Tue, 13 Mar 2012 10:08:12 -0700, > Eliot Miranda wrote: > > > > In this case runUntilErrorOrReturnFrom: aContext should return the > sender of the activation of Foo>test and the result to be returned (42). > But instead it answers the activation of Foo>test > > and nil. Hence the return in ContextPart>return: isn't simulated and > control passes to the next statement, ^666. > > > > Once again I'm drawn into the bowels of runUntilErrorOrReturnFrom: > > :) It is my nemesis. > > This seems close to the realm of magic to me. Thank you for looking > into it! > Alas, I find it near to magic too. I understand what's going on. The terminateTo: call in resume: doesn't trip the unwind-protect in runUntilErrorOrReturnFrom: (as it shouldn't; terminateTo: specifically doesn't run unwinds by design). So runUntilErrorOrReturnFrom: doesn't answer the right context to resume. It answers Foo>test instead of Foo>test's sender. What I don't understand is what is a valid criterion for determining these cases. I can hack the method, special casing it for ContextPart>return: and ContextPart>resume:, but that's not acceptable. So if anyone has the desire to pair on this let me know. Perhaps we could have a go at it over skype sometime soon (not today; already blown a lot of time looking at this ;) ). In any case I've attached two versions of runUntilErrorOrReturnFrom:, one instrumented, one not, containing a hack that gets the right answer (in this case). Yoshiki, you might play with the uninstrumented one to get you going. Hans-Martin, I think you're one of very few people who could shed light on this. To use the instrumented one (which prints its arguments and halts between evaluation and deciding what to return) step the debugger up to e.g. the send of return:, inspect thisContext (the context about to be sent return:) and set ContextPart's class var QuickStep to that context (in the inspector evaluate QuickStep := self). Then do step. At least the hack doesn't make things worse; the tests appear the same. So one thing to do is to play with the hack, ad see if it causes problems. Another thing to do is to think about the criterion in the hacked runUntilErrorOrReturnFrom: when one should return from the receiver's receiver, rather from aSender's sender. I'm cc'ing the Pharo list. Here's Yoshiki's original message and a substantive reply of mine: On Tue, Mar 13, 2012 at 3:27 AM, Yoshiki Ohshima <Yoshiki.Ohshima(a)acm.org> wrote: > Hello, > I noticed that step executing the following code in debugger yields > different results: > ------------------- > test > 3 < 4 ifTrue: [ > thisContext return: 42]. > ^ 666. > ------------------- > In the normal execution, you get 42 as expected, but if you debug it > and step execute, #return: does not actually return and you get 666. > It appears that the primitive for #terminateTo: is the culprit... -- Yoshiki On Tue, Mar 13, 2012 at 10:08 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Yoshiki, >From what I can see so far it is the return value from runUntilErrorOrReturnFrom: in complete: when the debugger executes test's return: call. i.e. the debugged process is in Foo>>test at pc 43: 37 <22> pushConstant: 3 38 <23> pushConstant: 4 39 <B2> send: < 40 <9B> jumpFalse: 45 41 <89> pushThisContext: 42 <21> pushConstant: 42 43 <E0> send: return: 44 <87> pop 45 <24> pushConstant: 666 46 <7C> returnTop The stack in the debugger is Process>>complete: Process>>completeStep: Debugger>>doStep and Process>complete: is complete: aContext "Run self until aContext is popped or an unhandled error is raised. Return self's new top context, unless an unhandled error was raised then return the signaler context (rather than open a debugger)." | ctxt pair error | ctxt := suspendedContext. suspendedContext := nil. "disable this process while running its stack in active process below" pair := ctxt runUntilErrorOrReturnFrom: aContext. suspendedContext := pair first. error := pair second. error ifNotNil: [^ error signalerContext]. ^ suspendedContext where the receiver is the activation of Foo>test, and aContext is the activation of ContextPart>return: (whose receiver is also the receiver of complete:, the activation of Foo>test). In this case runUntilErrorOrReturnFrom: aContext should return the sender of the activation of Foo>test and the result to be returned (42). But instead it answers the activation of Foo>test and nil. Hence the return in ContextPart>return: isn't simulated and control passes to the next statement, ^666. Once again I'm drawn into the bowels of runUntilErrorOrReturnFrom: :) It is my nemesis. -- best, Eliot -- best, Eliot

2 1

[Pharo-project] Gettext package, who?
by Hilaire Fernandes March 14, 2012

March 14, 2012

Who is maintaining the Gettext package? I remember someone volunteer to take over but I forgot who and where. I have a few fixes to get the gettext package working with 1.4, at least the exporter. Hilaire -- Dr. Geo -- http://www.drgeo.eu

1 0

[Pharo-project] [update 1.4] #14391
by Marcus Denker March 14, 2012

March 14, 2012

14391 ----- Issue 5480: Remove a method in PluggableIconListMorph http://code.google.com/p/pharo/issues/detail?id=5480 Issue 5471: extend time for shouldntTakeLong: http://code.google.com/p/pharo/issues/detail?id=5471 Issue 5456: ClassBuilder depends on Text http://code.google.com/p/pharo/issues/detail?id=5456 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14390
by Marcus Denker March 14, 2012

March 14, 2012

14390 ----- I Issue 5473: Auto accept and update lists in MCWorkingCopyBrowser and MCFileRepositoryVersionInspectorBrowser2 http://code.google.com/p/pharo/issues/detail?id=5473 -- Marcus Denker -- http://marcusdenker.de

1 0

March 14, 2012

1 0