[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Before releasing Gambas 3.21.4 - Timers test failure


Le 10/03/2026 à 22:55, Jussi Lahtinen a écrit :

    Indeed. I don't know what these tests are supposed to check. Especially
    the Timer test #5, which fails if the 'Sleep' instruction does now wait
    the specified time.

    This is stupid, as by definition, sleeping can be interrupted, and so
    may not wait at all, and the duration of the sleep may be rounded up,
    depending how the system behaves.

    I think this test should be removed.


Not sure, but if they are taken from the tests I made, they check if the commands work as expected. I don't think Sleep command should be interruptible, Wait is for that. There should be some tolerance for rounding up.


Jussi


I checked, and indeed the Sleep instruction repeats the system call until the specified time elapses.

So the difference between the specified time and the actual duration of the instruction should come from the system.

REgards,

--
Benoît Minisini.


Follow-Ups:
Re: Before releasing Gambas 3.21.4 - Timers test failureJussi Lahtinen <jussi.lahtinen@xxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - Timers test failureChristof Thalhofer <chrisml@xxxxxxxxxxx>
References:
Before releasing Gambas 3.21.4Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - IDE http freezeChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - IDE http freezeBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - IDE http freezeChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - Timers test failureChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - Timers test failureChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - Timers test failureBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: Before releasing Gambas 3.21.4 - Timers test failureJussi Lahtinen <jussi.lahtinen@xxxxxxxxx>