-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.I-flaky-testIssue: A test is flaky/unreliable/spuriously failsIssue: A test is flaky/unreliable/spuriously failsT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
Test tests/ui/threads-sendsync/tcp-stress.rs
sometimes fails for reasons unrelated to the changes being tested.
Examples:
- Rollup of 13 pull requests #144850 (comment)
- Shard AllocMap Lock #136115 (comment)
- Fix HashMap not displaying correctly in VS debugger #93626 (comment)
The failure is triggered by an arbitrary hard-coded timeout of 30 seconds, so this probably happens when the runner is temporarily distracted by other things and can't clean up 200 threads in time.
saethlin and jieyouxu
Metadata
Metadata
Assignees
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.I-flaky-testIssue: A test is flaky/unreliable/spuriously failsIssue: A test is flaky/unreliable/spuriously failsT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.