[Vm-dev] some stupid failures

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Tue Jan 5 08:08:26 UTC 2021


Hi all,
sometimes, some build fail for just 1 test...

Here https://travis-ci.com/github/OpenSmalltalk/opensmalltalk-vm/jobs/468407844
a squeak.stack.v3

RenderBugz
 ✗ #testSetForward (7ms)
TestFailure: Block evaluation took more than the expected 0:00:00:00.004
RenderBugz(TestCase)>>assert:description:
RenderBugz(TestCase)>>should:notTakeMoreThan:
RenderBugz(TestCase)>>should:notTakeMoreThanMilliseconds:
RenderBugz>>shouldntTakeLong:
RenderBugz>>testSetForward ...shouldntTakeLong: [ t forwardDirection: 180.0 .
self assert: ( t forwardDirection = 0.0 )  ]
RenderBugz(TestCase)>>performTest

4ms, really? On C.I. infrastructure, anything can happen...
Do we really want to keep this kind of test?
We eventually could once startup performance is known (see
isLowerPerformance discussion on squeak-dev), but in the interim, I
suggest we neutralize this specific test in Smalltalk-CI.


More information about the Vm-dev mailing list