You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Test] CompletableIsolatedTest.repeatNormal has a wall-clock-dependent call-count assertion #8372
CompletableIsolatedTest.repeatNormal depends on wall-clock timing for an exact call-count assertion.
The test schedules disposal after 1100 ms, while the callable sleeps for 200 ms on each invocation, and immediately asserts exactly 6 calls. This boundary is sensitive to scheduler and machine timing jitter.
Evidence from local verification
Using both Temurin and Zulu 26.0.2.1, Gradle 9.9.0, on Windows:
During full-suite runs of 14,296 JUnit tests, the test failed intermittently with calls count mismatch:
@Isolated prevents interference from other tests, but does not remove timing jitter in this test itself.
Suggested direction
Please consider making the synchronization deterministic (for example, a scheduler/latch-based arrangement) or otherwise avoiding a hard exact-count assertion at a real-time boundary.
AI disclosure: Kimi Code assisted with reproducing and analyzing the timing issue and drafting this report. No production-code patch is attached.
Activity