The service test RedisBridgePairingStore > renews the cleanup claim while a shared-keyspace scan is in flight is timing-sensitive under full-suite CI load.
It configures a 30 ms claim TTL, renews every 10 ms, sleeps 80 ms inside the scan, and asserts after 45 ms. Event-loop stalls longer than the TTL can expire the mocked Redis claim before the renewal callback runs, causing Legacy pairing cleanup claim was lost even though the production logic and the test target are unchanged.
Please make the test deterministic (for example, coordinate renewal/expiry through a controllable fake) or use timing margins that tolerate CI scheduling while still proving the claim is renewed during the scan.
The service test
RedisBridgePairingStore > renews the cleanup claim while a shared-keyspace scan is in flightis timing-sensitive under full-suite CI load.It configures a 30 ms claim TTL, renews every 10 ms, sleeps 80 ms inside the scan, and asserts after 45 ms. Event-loop stalls longer than the TTL can expire the mocked Redis claim before the renewal callback runs, causing
Legacy pairing cleanup claim was losteven though the production logic and the test target are unchanged.Please make the test deterministic (for example, coordinate renewal/expiry through a controllable fake) or use timing margins that tolerate CI scheduling while still proving the claim is renewed during the scan.