On Feb 25, 2013, at 8:21 PM, Dale Henrichs <dhenrich@vmware.com> wrote:
I think that the suspendAllWhile: call is important because a) some Metacello tests are sensitive to packages getting marked dirty or other events getting triggered â¦
Christophe tried to removed them completely but there were other problems. I was not with him so I do not have all the info. What we noticed is that suspendAllWhile: is not equilavent because the events have been "clarified". Stef
----- Original Message ----- | From: "Christophe Demarey" <Christophe.Demarey@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, February 21, 2013 1:26:31 AM | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | | Dale | | we run the tests simply rewriting runCase as | | runCase | | original | | (self doSilently) ifFalse: [ ^super runCase ]. | original := MetacelloPlatform current bypassGoferLoadUpdateCategories. | [ | MetacelloPlatform current bypassGoferLoadUpdateCategories: true. | ^ SystemAnnouncer uniqueInstance suspendAllWhile: [ super runCase ] | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories: | original ] | | but it seems that we do not have the same behavior between the two | | runCase | | original | | (self doSilently) ifFalse: [ ^super runCase ]. | original := MetacelloPlatform current bypassGoferLoadUpdateCategories. | [ | MetacelloPlatform current bypassGoferLoadUpdateCategories: true. | ^ super runCase ] | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories: | original ] | | So we will run all the tests | | Stef