From 2dbb406ac0968addc62f0d40a2a56151fb3c788a Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 02:17:45 -0643 Subject: [PATCH] omamobile-shell test/owl-idle: the paused-tick check no longer depends on the wall clock tickDelay() returns the time to the next boundary, so with the home screen paused the next tick can legitimately be less than a tick away: in the last second of every hiddenTickMs period, which is 10 percent of the clock at 10000 and 1000 ms. The check then asserts something untrue and the run fails, as it did in CI with 554 ms (a clock 9451 ms into its period). Step over that boundary before pausing. --- packages/omamobile-shell/test/owl-idle.qml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/packages/omamobile-shell/test/owl-idle.qml b/packages/omamobile-shell/test/owl-idle.qml index 28645fe56..ffbd31818 100644 --- a/packages/omamobile-shell/test/owl-idle.qml +++ b/packages/omamobile-shell/test/owl-idle.qml @@ -130,6 +130,13 @@ Item { function test_5_paused_home_stops_frames_and_slows_the_tick() { verify(scheduler.tickInterval <= Phone.CLOCK.tickMs + 5) + // tickDelay() returns the time to the next boundary, so in the last + // second of a hidden period the paused delay is legitimately shorter + // than a tick. Step over that boundary before pausing, or the check + // below asserts something untrue about one second in every + // hiddenTickMs (it failed in CI that way). + if (Phone.tickDelay(Date.now(), true) <= Phone.CLOCK.tickMs + 5) + wait(Phone.CLOCK.tickMs + 20) scheduler.paused = true tryVerify(function() { return !scheduler.framing }, 500, "covered or off: no frames") verify(scheduler.tickInterval > Phone.CLOCK.tickMs + 5, "the tick slows while paused (" + scheduler.tickInterval + " ms)")