Re: Issue 3575 in pharo: [Failing Tests] Obsolete classes after tests

Updates:
        Summary: [Failing Tests] Obsolete classes after tests

Comment #6 on issue 3575 by [hidden email]: [Failing Tests] Obsolete  
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

(No comment was entered for this change.)

Comment #7 on issue 3575 by [hidden email]: [Failing Tests] Obsolete  
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

Hi, some of the obsolete classes are being held onto by Tools->Recent  
Messages. Look at the bottom of the list.

Comment #8 on issue 3575 by [hidden email]: [Failing Tests] Obsolete  
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

As this just happens after running all tests, I propose to remove the  
Obselete classes test in 1.1 and 1.2 and move the problem to be fixed in 1.3

(the tests are messy wrt. to changes to the system anyway, packages are  
dirty, files are written...)

Updates:
        Labels: -Milestone-1.2-DevImage

Comment #9 on issue 3575 by [hidden email]: [Failing Tests] Obsolete  
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

in 12339

Updates:
        Labels: -Milestone-1.1.2-DevImage

Comment #10 on issue 3575 by [hidden email]: [Failing Tests]  
Obsolete classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

in 11421

Updates:
        Status: Closed

Comment #11 on issue 3575 by [hidden email]: [Failing Tests]  
Obsolete classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575

(No comment was entered for this change.)