-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Cleanup "no panic support" tests #135923
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
Labels
A-panic
Area: Panicking machinery
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-cleanup
Category: PRs that clean code up or issues documenting cleanup.
E-medium
Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
Tagging as E-medium because this might involve running multiple try-jobs against certain CI jobs. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 3, 2025
Remove redundant `//@ ignore-{wasm,wasm32,emscripten}` in tests Follow-up to rust-lang#135926. When `//@ needs-{unwind,subprocess}` are the suitable capability guards. Resolves rust-lang#135923. r? `@ghost` try-job: test-various
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 3, 2025
Remove generic `//@ ignore-{wasm,wasm32,emscripten}` in tests Follow-up to rust-lang#135926. In favor of capability-based guards `//@ needs-{unwind,subprocess}`. Resolves rust-lang#135923. r? `@ghost` try-job: test-various
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Feb 3, 2025
Remove generic `//@ ignore-{wasm,wasm32,emscripten}` in tests Follow-up to rust-lang#135926. In favor of capability-based guards `//@ needs-{unwind,subprocess}`. Resolves rust-lang#135923. r? `@ghost` try-job: test-various
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 4, 2025
Rollup merge of rust-lang#136476 - jieyouxu:panic-panic-panic, r=lcnr Remove generic `//@ ignore-{wasm,wasm32,emscripten}` in tests Follow-up to rust-lang#135926. In favor of capability-based guards `//@ needs-{unwind,subprocess}`. Resolves rust-lang#135923. r? ``@ghost`` try-job: test-various
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-panic
Area: Panicking machinery
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-cleanup
Category: PRs that clean code up or issues documenting cleanup.
E-medium
Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
There are a bunch of tests that say
ignore-wasm
orignore-emscripten
orignore-$platform
with a comment "no panic support" or "no panic". It would be good to audit them and see if one or more of the following capability-based conditional test execution directives can be used instead://@ needs-unwind
//@ needs-threads
//@ needs-subprocess
1If those are not sufficient, it would be good to improve the ignore reason anyway.
Footnotes
I'm still working on implementing this directive over at compiletest: add a
needs-subprocess
directive #128295. ↩The text was updated successfully, but these errors were encountered: