Come on, nobody plays to get the build green?<br><br><div class="gmail_quote">On Wed, Jul 4, 2012 at 9:24 PM, Guillermo Polito <span dir="ltr">&lt;<a href="mailto:guillermopolito@gmail.com" target="_blank">guillermopolito@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br><br>I&#39;ve done a little fix today that allows monticello tests to run -green btw- :). <a href="http://code.google.com/p/pharo/issues/detail?id=6273" target="_blank">http://code.google.com/p/pharo/issues/detail?id=6273</a><br>
So, I expect this will put us 11 tests closer to a green build.<br>
<br><br>This was a problem related with the monticello-mocks and monticellomocks packages.<br>There are problems still remaining, like, as giving an example:<br><br>- MCMock is categorized Monticello-Mocks, but is in the Monticello RPackage...<br>

<br>That happens with all the classes in the Monticello-Mocks category.� The root of the problem is that we have some strange objects installed as packages (PackageInfo registrations).� Have a look at the result of:<br><i><br>

PackageInfo named: &#39;Monticello-Mocks&#39;.</i><br><br>Seems MC tests have side effects over the system.<br><br><br>Guille<br>
</blockquote></div><br>