Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package Monticello leaves Obsolete class after tests
Updates: Summary: [Failing Tests] Package Monticello leaves Obsolete class after tests Comment #3 on issue 3575 by marcus.d...@gmail.com: [Failing Tests] Package Monticello leaves Obsolete class 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 Milestone-1.1.2-DevImage Comment #4 on issue 3575 by marcus.d...@gmail.com: [Failing Tests] Package Monticello leaves Obsolete class after tests http://code.google.com/p/pharo/issues/detail?id=3575 (No comment was entered for this change.)
Comment #5 on issue 3575 by guillerm...@gmail.com: [Failing Tests] Package Monticello leaves Obsolete class after tests http://code.google.com/p/pharo/issues/detail?id=3575 Actually, the Obsolete class is AnObsoleteAutoGeneratedClassForTestingSystemChanges. I dived a little into the tests. The test that is creating the obsolete class is: ChangeHooksTest>>testClassCommentedEvent self systemChangeNotifier notify: self ofAllSystemChangesUsing: #classCommentedEvent:. generatedTestClass comment: self commentStringForTesting. self checkForOnlySingleEvent The other tests of this class work just well. I dived into TraitDescription>>comment: to see if it keeps references to the class or an instance, but I didn't found anything significant...
participants (1)
-
pharo＠googlecode.com