> On 6 Jan 2018, at 20:08, Alistair Grant <[email protected]> wrote: > > Hi Ben, > > On 6 January 2018 at 12:09, Ben Coman <[email protected]> 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" >> >> 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. > > Which platform and image? > > Pharo 7.0 > Build information: > Pharo-7.0+alpha.build.410.sha.aa40385cd6fee69bb51d4a3afcacfb5f91eed206 > (32 Bit) > Ubuntu 16.04 > > 14915 run, 14859 passes, 31 skipped, 50 expected failures, 5 failures, > 1 errors, 0 unexpected passes > Failures: > ReleaseTest>>#testMethodsWithUnboundGlobals > TonelWriterTest>>#testWriteSnapshot > ReleaseTest>>#testUnpackagedClasses > ReleaseTest>>#testNoEmptyPackages > ReleaseTest>>#testThatAllMethodsArePackaged > > Errors: > ZnClientTests>>#testRedirect
Hmm, strange. Does it failed each time ? It does not fail for me (macOS). Furthermore, all Zinc tests are green https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/ > Cheers, > Alistair > > > >> 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.
