[Moose-dev] Re: Moose release 4.1

I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose. Beside this, all the tests of the tools directly used by Moose are green. Well done guys! Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning. I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow. Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8. I am happy with this Cheers, Alexandre On 14 Sep 2010, at 13:16, Laval Jannik wrote: -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.