Hi adrian who is working on what? On Mar 27, 2010, at 6:17 PM, Adrian Lienhard wrote:
Hi all,
What results do you get when running all tests in Pharo and PharoCore 1.0 on Mac/Windows/Linux?
Lukas has MCPackageTest>>#testUnload failing on Hudson (a Linux server, I assume). When running the tests locally on the Mac, the test BlockContextTest>>#testTrace fails. But only the first time. Apparently ContextPart>>#trace: is broken [1].
When I run all tests in Pharo1.0 on a Mac VM 4.2.3beta1U the first time I get no failures. When running the second time I get following failures:
MCInitializationTest>>testWorkingCopy
when I run this test twice is is green "self debug: #testWorkingCopy"
MCSnapshotTest>>testInstanceReuse same here self debug: #testInstanceReuse
ReleaseTest>>testObsoleteClasses probably another test create a class and it is not cleaned up.
I think that theses tests do not show bugs but probably badly designed tests. So why don't you move them to expected failures and we release 1.0?
ProcessspecificTest>>testDynamicVariable ProcessspecificTest>>testLocalVariable
If I then run only the above, they all pass.
So there is certainly something fishy with the tests or how they are run.
I would like to have a reliable, green test suite for Pharo 1.0. Can you report the results you get including the VM/platform? Any idea why the results are not stable?
Thanks, Adrian
[1] http://code.google.com/p/pharo/issues/detail?id=2210
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project