From 03b0639ae821a573f71eb59e9808587bc42cdec8 Mon Sep 17 00:00:00 2001 From: Mobeen Abdullah Date: Sun, 16 Aug 2026 19:44:56 +0500 Subject: [PATCH] test(root): bound the rewound clock rather than pinning it --- .../canvas/geometry-settle-matches-the-canvas.test.ts | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/e2e/tests/canvas/geometry-settle-matches-the-canvas.test.ts b/e2e/tests/canvas/geometry-settle-matches-the-canvas.test.ts index 9300d4bafa..833ebe273a 100644 --- a/e2e/tests/canvas/geometry-settle-matches-the-canvas.test.ts +++ b/e2e/tests/canvas/geometry-settle-matches-the-canvas.test.ts @@ -1551,7 +1551,12 @@ test.describe("the drop-zone geometry the probe waits on", () => { }); expect(applied).not.toBeNull(); expect(applied?.rate).toBe(1); - expect(applied?.currentTime).toBe(-30000); + // A BOUND, not an equality. The clock keeps running between the assignment and the read, so + // an exact comparison measures how long that round trip took — it held locally and lost a + // frame (16.7ms) on CI. What makes this the case it claims to be is that the effect is rewound + // far into the past, which is stable; the exact value is not, and asserting it tests the + // runner rather than the rewind. + expect(applied?.currentTime).toBeLessThan(-29000); // The two readings a naive live span would use, both still describing the stylesheet. expect(applied?.activeDuration).toBe(20000); expect(applied?.delay).toBe(0);