On Fri, 10 Apr 2015, Bert Freudenberg wrote:

>
>       On 10.04.2015, at 17:21, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
> 
> This sounds like scories left by another TestCase…
> 
> 
> Yep.
>
>       So natural questions arising are
>       - doesn't it depend on the ordering of test cases?
> 
> 
> It should.
>
>       - How are TestCase ordered exactly?
> 
> 
> I though TestRunner randomized the execution order.
> Good News is that I can reproduce (part of) the problem simply by running all tests even on my Mac. After that I inspect "SystemNavigation default obsoleteClasses” and get some. Here’s what PointerFinder tells me holds onto them:

IIRC the tests are run one by one on the build server, not from the 
TestRunner.

> 
> 
> globals: Environment
> declarations: IdentityDictionary
> #World -> PasteUpMorph
> submorphs: Array
> 7: PluggableSystemWindow (1734)
> model: TestRunner
> result: TestResult
> passed: OrderedCollection
> array: Array
> 550: ClassVarScopeTest
> parent: AnObsoleteClassVarScopeParent class
> 
> Apparently, that test modifies its own parent class?!

I doubt it. It creates three classes. But that problem should be gone by 
now. The TestCase instance held references to the created classes.


Levente

> 
> I did not see the obsolete MCMock* classes on the Mac, though.
> 
> - Bert -
> 
> 
>