On Fri, Jan 8, 2016 at 11:27 PM, Vincent BLONDEAU <vincent.blondeau@polytech-lille.net> wrote:

-----Original Message-----
From: moose-dev-bounces@list.inf.unibe.ch
[mailto:moose-dev-bounces@list.inf.unibe.ch] On Behalf Of Tudor Girba
Sent: vendredi 8 janvier 2016 22:56
To: Moose-related development
Subject: [Moose-dev] 4 tests failing

Hi,

Hi,

It looks like in the Spur image, the ghost instances of GTInspector are
gone.

Or willingly deleted? See the configuration of Moose6.0:

Nope. These tests are run twice. The first time they will fail as there are instances of the inspector in the image from other tests. After all tests are done we delete the results of these tests, run garbageCollect a few times, and run them again.

Cheers,

Andrei

./pharo $JOB_NAME.image test --junit-xml-output "GT-.*"

rm -rf GT-Tests-Release-*
rm -rf GTFinalReleaseTest-*

./pharo $JOB_NAME.image eval --save "3 timesRepeat: [Smalltalk
garbageCollect]"
./pharo $JOB_NAME.image eval --save "3 timesRepeat: [Smalltalk
garbageCollect]"
./pharo $JOB_NAME.image test --junit-xml-output GT-Tests-Release

./pharo $JOB_NAME.image eval --save "SystemSettingsPersistence cleanUp"

So, now we have only 4 tests failing, and they all seem to be related to a
possible problem with become:. I am not yet sure what the solution is, but I
raised this issue on the Pharo mailing list.

Thanks !

Cheers,
Vincent

Cheers,
Doru

--
www.tudorgirba.com
www.feenk.com

"It's not what we do that matters most, it's how we do it."

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev