On 6 January 2018 at 19:09, Ben Coman <btc@openinworld.com> wrote:

It great having a CI system to check all our tests a passing,
but I thought I'd go old school and run them from the TestRunner GUI
and found in a fresh latest Pharo 7 there are "128 failures, 63 errors"

So that was Pharo64bit.

Pharo32bit is better with only has only "1 failures, 20 errors".

So what is the CI dependency of the 32 bit and 64 bit Images?

Do they both run tests independently?

cheers -ben

��

This one is interesting...
ArrayTest>>test0FixtureAsSetForIdentityMultiplinessTest
| anElement res |
self elementsCopyNonIdenticalWithoutEqualElements.
anElement := self elementsCopyNonIdenticalWithoutEqualElements anyOne.
self deny: anElement copy == anElement.�� "<<<<FAILS"

where anElement ==> SmallFloat64 (1.5)
so the deny fails.

It seems that the test setUp is wrong since #elementsCopyNonIdenticalWithoutEqualElements��
does not return a collection (of elements for which copy is not identical ) without equal elements:"

This seems like a permanent error rather than a transient one.
How does this slip through CI testing?
and what can be done about cleaning this up?

cheers -ben

P.S. With the loss of method version info is impossible to guess when this may have been introduced, to guess which Issue it was related to, to guess how I might approach fixing this myself.