If you check the report, you see your code broke a test.

According to the test name, I would say that your method should be added to TBehavior, and not Behavior directly.

:)

Ben

On 05 Jan 2014, at 09:56, Alexandre Bergel <alexandre.bergel@me.com> wrote:

Hi!

I have proposed a method Behavior>>dependentClasses, but apparently the Monkey is not really happy about it. I doubt the error in the generated report stems from this change.
https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/validationReport.html

No idea how to proceed from there.

Cheers,
Alexandre

On Jan 5, 2014, at 6:42 AM, Pharo Issue Tracker <do-not-reply@pharo.fogbugz.com> wrote:


Ulysse The Galactic Monkey From Outer Spaceedited Case 12566: Added Behavior>>#dependentClasses:

Bug in  Kernel: 1. Pharo Image

Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/validationReport.html
Errors: 1 | Warnings: 1 |

Status changed:
Resolved (Monkey is checking)    Work Needed (Failing Test)

Priority: 5 � Fix If Time Status: Work Needed (Failing Test)
Assigned to: Alexandre Bergel Milestone: Pharo3.0


Go to Case

Don't want FogBugz notifications anymore? Update your preferences.



--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.