Hi Ben, ok. I took the newest image from the inria file server (30556) tested, closed it because it was ok.
While testing I found a new one. https://pharo.fogbugz.com/f/cases/12111/Date-readFrom-4-2-2013-readStream-pattern-d-m-yy-4-February-2020 This is not important for me but I think this is not correct. If the pharo developers do not want to get such "inch picker" (Korinthenkacker) bug entries, plese delete it :-) Regards Sabine On Fri, Nov 8, 2013 at 11:33 AM, btc [via Smalltalk] < [email protected]> wrote: > Sabine Knöfel wrote: > > Hi Clement, > > I did not fix it, I only got the mail that it was fixed. Ok, I will do > nothing;-) Thanks. > > The ermergency evaluator is in nautilus. OS: Windows. > MessageNot Understood: ToolRegistry>>shortcuts > > Regards > Sabine > > > > Actually, You should have received a mail previous to that one that said > "Resolved ( Fix review needed)" > which I think is the point that the monkey picks it up. But the monkey > only tests it doesn't break anything. It doesn't test that it fixes your > problem. I think its worthwhile that you try the fix yourself, but just > report what find as a standard comment. Do the same with the image that > the fix is integrated into, and then you can close the Case, if someone > hasn't already beat you to it. > > cheers -Ben > > > On Fri, Nov 8, 2013 at 10:51 AM, Clément Bera [hidden email] > <http://user/SendEmail.jtp?type=node&node=4720231&i=0>wrote: > > > > Hello, > > > *1) I asssume that my task is to test it? If the test would be ok, should > I click on resolve in Fog Buz?* > > So basically when you resolved your bug, you added a slice and put the > status fix review needed. > > Then, the monkey (which is a script) took the latest pharo image, added > your slice and ran all the tests. If all the tests of the image passed with > your new slice (which is the case), the monkey put the status Fix reviewed > by the monkey, that you have now, and this means your fix does not break > any test in the image. If your slice had broken tests, the monkey would > have put back the status to Work needed. > > So you do not have to do anything right now. Someone will have a look to > review your code and put the status to fix to include (but this should not > be you), this reviewing step is sometimes skipped (it is usually skipped > when the fix is minor or obvious). Lastly, an integrator (usually Marcus, > but it could be Esteban or Stef) will integrate it. > > Your fix should be integrated in the next few days if the code review is > ok. > > > > *2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, I get an emergency evaluator, so I can not test it. Perhaps not > yet time totest? Wait? Is the emergency evaluator reason interesting for > you?* > > No clue. I tried and I had no emergency evaluator. By browser you mean > Nautilus right ? > > > > 2013/11/8 Sabine Knöfel [hidden email] > <http://user/SendEmail.jtp?type=node&node=4720231&i=1> > > Hi, > > I got the Fog Buzz message below. > > 2 Questions: > > 1) I asssume that my task is to test it? If the test would be ok, should I > click on resolve in Fog Buz? > 2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, > I get an emergency evaluator, so I can not test it. Perhaps not yet time > to > test? Wait? Is the emergency evaluator reason interesting for you? > > I want to contribute:-) please tell my how :-) > > Regards > Sabine > > ############################## > A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. > > Case ID: 11222 > Title: Date readFrom:pattern: (year 2 decimals not 20xx but 00xx) > Status: Resolved (Fix Reviewed by the Monkey) > Category: Bug > Project: Chronology > Area: 1. Pharo Image > Priority: 5 - Fix If Time > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Sabine Knöfel > > URL: https://pharo.fogbugz.com/f/cases/11222 > > > Changes: > Added tag 'Validated in 30555'. > > > > -- > View this message in > context:http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp4720186.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp4720186p4720231.html > To unsubscribe from Text fixed Bug? emergency evaluator comes up in 3.0, > click > here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4720186&code=c2FiaW5lLmtub2VmZWxAZ21haWwuY29tfDQ3MjAxODZ8MTA0OTM5MTYx> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp4720186p4720254.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
