On Windows (and other platforms) we have the annoying case that the Ticker test
misses a tick or two due to time jitter in the virtual machines, like here:
[failure] 20230406 16:21:37.700000
Test: TEST_TICKER_THREE_ARGS_STRING_TRIGGER
Class: Ticker.testGroup
File: ...\ooRexx\base\class\Ticker.testGroup
Line: 117
Failed: assertTrue
Expected: 1
Actual: 0
Message: should have triggered once, but triggered 0 times
As a result the test suite hangs at the very last line, after completion of the
test. The final result of all tests is there but there are three running dots
at the bottom indicating the test is still running.
I have set the tests to time out eventually but it would be nice if we could
find a way to either kill a missing ticker (it is present in the task list;
when killed manually the test suite finishes) or find a way to avoid that a
ticker hangs indefinitively.
Since this is most likely a problem with the test suite and not ooRexx itself I
did not make it a bug report. It rarely happens on a physical machine, just
when running in a VM.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
