-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Use realstd current thread static variables in tests #150131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
rustbot has assigned @Mark-Simulacrum. Use |
This comment has been minimized.
This comment has been minimized.
|
r=me with a rebase Can you clarify why this should be beta-nominated? It's not clear to me what regression it's fixing. |
6b430c3 to
abbbd77
Compare
This comment has been minimized.
This comment has been minimized.
|
Thanks for the review. The stdlib's cc: @Mark-Simulacrum (don't have the privileges for bors commands) |
|
@sardok: 🔑 Insufficient privileges: Not in reviewers |
|
@Mark-Simulacrum can you please take a look at the PR? This is (still) failing in nightly, and the beta release is approaching quickly. |
|
@bors r+ |
…imulacrum Use realstd current thread static variables in tests Fixes rust-lang#150053. This PR basically exports `thread::current::CURRENT` & `thread::current::ID*` static variables and be referred to them when testing. I also added a minor refactoring which collects symbols referred as `readlstd::...` in `test_internals` module. If approved, i would kindly ask this PR to be beta nominated. Thank you.
…imulacrum Use realstd current thread static variables in tests Fixes rust-lang#150053. This PR basically exports `thread::current::CURRENT` & `thread::current::ID*` static variables and be referred to them when testing. I also added a minor refactoring which collects symbols referred as `readlstd::...` in `test_internals` module. If approved, i would kindly ask this PR to be beta nominated. Thank you.
|
Checking for the failure at #150856 (comment) @bors2 try jobs=aarch64-gnu-llvm-20-1 |
|
Unknown command "2". Run |
This comment has been minimized.
This comment has been minimized.
Use realstd current thread static variables in tests try-job: aarch64-gnu-llvm-20-1
…imulacrum Use realstd current thread static variables in tests Fixes rust-lang#150053. This PR basically exports `thread::current::CURRENT` & `thread::current::ID*` static variables and be referred to them when testing. I also added a minor refactoring which collects symbols referred as `readlstd::...` in `test_internals` module. If approved, i would kindly ask this PR to be beta nominated. Thank you.
…imulacrum Use realstd current thread static variables in tests Fixes rust-lang#150053. This PR basically exports `thread::current::CURRENT` & `thread::current::ID*` static variables and be referred to them when testing. I also added a minor refactoring which collects symbols referred as `readlstd::...` in `test_internals` module. If approved, i would kindly ask this PR to be beta nominated. Thank you.
|
Investigating failure in rollup: #150914 (comment) @bors try jobs=aarch64-gnu-llvm-20-1 |
This comment has been minimized.
This comment has been minimized.
Use realstd current thread static variables in tests try-job: aarch64-gnu-llvm-20-1
|
Hmm, looks like I wasn't the first person to suspect this PR for that failure, and the previous try job was fine. Maybe the failure is flaky? I'll re-run a try job on the rollup that failed, to double-check. |
This comment has been minimized.
This comment has been minimized.
|
💔 Test for fbb646e failed: CI. Failed jobs:
|
|
@bors r- |
|
Commit abbbd77 has been unapproved. |
abbbd77 to
a5fb2de
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
I've been looking into the As far as I can see, the test runner crashes during io:: tests, which suggests the thread ID refactoring in this PR might be the cause. @Mark-Simulacrum, how should I proceed? Does it make sense to restrict the thread ID refactoring to the SGX target? cc @davidtwco as lead of the aarch64-unknown-linux-gnu target. |
|
I was able to reproduce a failure locally on my M1 Mac using the command In CI, As I understand it, there are two implementations of |
Fixes #150053. This PR basically exports
thread::current::CURRENT&thread::current::ID*static variables and be referred to them when testing. I also added a minor refactoring which collects symbols referred asreadlstd::...intest_internalsmodule.If approved, i would kindly ask this PR to be beta nominated.
Thank you.