Skip to content

Conversation

@ChrisDenton
Copy link
Member

@ChrisDenton ChrisDenton commented Oct 19, 2025

I think the sporadic Windows test failures may be due to thread scheduling under high contention so workaround this by synchronising the two threads at the start.

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Oct 19, 2025
@joboet
Copy link
Member

joboet commented Oct 20, 2025

That would require the spawning thread to not be scheduled for 2 seconds, which seems unlikely. I've opened #147910 as an alternative.

@ChrisDenton
Copy link
Member Author

Hm, fair. I do think it's technically possible but indeed unlikely. I'll close this in favour of yours.

@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 20, 2025
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 20, 2025
… r=ChrisDenton

handle spurious returns of `wait_timeout` in test

Fixes rust-lang#147885
Closes rust-lang#147871

`wait_timeout` is allowed to spuriously return, hence the `timeout_nanoseconds` must not assume that the wakeup resulted from a `notify_all()`.
bors added a commit that referenced this pull request Oct 20, 2025
handle spurious returns of `wait_timeout` in test

Fixes #147885
Closes #147871

`wait_timeout` is allowed to spuriously return, hence the `timeout_nanoseconds` must not assume that the wakeup resulted from a `notify_all()`.
RalfJung pushed a commit to RalfJung/miri that referenced this pull request Oct 22, 2025
handle spurious returns of `wait_timeout` in test

Fixes rust-lang/rust#147885
Closes rust-lang/rust#147871

`wait_timeout` is allowed to spuriously return, hence the `timeout_nanoseconds` must not assume that the wakeup resulted from a `notify_all()`.
github-actions bot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Oct 27, 2025
handle spurious returns of `wait_timeout` in test

Fixes rust-lang/rust#147885
Closes rust-lang/rust#147871

`wait_timeout` is allowed to spuriously return, hence the `timeout_nanoseconds` must not assume that the wakeup resulted from a `notify_all()`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants