Updates:
Status: Closed
Comment #11 on issue 3575 by marcus.d...@gmail.com: [Failing Tests]
Obsolete classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575
(No comment was entered for this change.)
Updates:
Labels: -Milestone-1.1.2-DevImage
Comment #10 on issue 3575 by marcus.d...@gmail.com: [Failing Tests]
Obsolete classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575
in 11421
Updates:
Labels: -Milestone-1.2-DevImage
Comment #9 on issue 3575 by marcus.d...@gmail.com: [Failing Tests] Obsolete
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575
in 12339
Comment #8 on issue 3575 by marcus.d...@gmail.com: [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
Comment #7 on issue 3575 by m...@mjr104.co.uk: [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.
Updates:
Summary: [Failing Tests] Obsolete classes after tests
Comment #6 on issue 3575 by guillerm...@gmail.com: [Failing Tests] Obsolete
classes after tests
http://code.google.com/p/pharo/issues/detail?id=3575
(No comment was entered for this change.)
