[Pharo-project] The monkey ...

Guillermo Polito guillermopolito at gmail.com
Thu Jul 5 04:03:45 EDT 2012


That was integrated 4 versions ago :).

Now, about the extra state for unexpected monkey failures, I think we can
tag issues with whatever tag we want, even if they are not configured in
the engine.  But the creator must make himself responsible of doing that...
Something like "ManualReviewNeeded" probably...

Guille

On Thu, Jul 5, 2012 at 8:45 AM, Torsten Bergmann <astares at gmx.de> wrote:

> Looks like our monkey is not able to read important notes before filing in
> changeset ;)
>
> see http://code.google.com/p/pharo/issues/detail?id=6139
>
>
> IMPORTANT NOTE:
> ===============
> The fix is using an utility method from the fix for isse #6138
> Therefore the attached fix requires "ProposedFix.cs" from
> http://code.google.com/p/pharo/issues/detail?id=6138
>
> Please check manually.
>
> Can we have an issue state: THE_MONKEY_RUNS_OUT_OF_BANANA
> so they get integrated
>
> I tested on different machines - IMHO the fixes for
> #6138 and #6139 are safe to integrate.
>
> Thx
> T.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120705/c5f63b1a/attachment-0001.html>


More information about the Pharo-dev mailing list