chore(rust): widen sleep gap in flaky Async.Sleep test#4573
Merged
Conversation
The test relied on Async.Sleep(100) finishing before Async.Sleep(300), but the 200ms gap is not robust on loaded CI runners — the second task can be queued >200ms after the first, inverting the order. Widen the gap to 100ms vs 1000ms. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Async.Sleep workstest intests/Rust/tests/src/AsyncTests.fsis timing-flaky on CI. It relies onAsync.Sleep(100)finishing beforeAsync.Sleep(300), but on a loaded runner the second task can be queued >200ms after the first, inverting the order (e.g. build-rust no_std on PR #4571 saw300100instead of100300).Test plan
build-rustjobs (default, threaded, no_std).Async.Sleepordering across two concurrent tasks.🤖 Generated with Claude Code