-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Detect panic strategy using rustc --print cfg
#102134
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jyn514 (or someone else) soon. Please see the contribution instructions for more information. |
r? @bjorn3 |
Could you try removing all test directives that exclude wasm32 when this is done because of unwinding not being supported on wasm? And maybe see if the same is done for other platforms? That would also allow testing this PR works in the first place. |
src/test/ui/async-await/issues/issue-65419/issue-65419-async-fn-resume-after-panic.rs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me with the above comment fixed.
@bors r+ |
Detect panic strategy using `rustc --print cfg` Instead of relying on a command line parameter, detect if a target is able to unwind or not. Ignore tests that require unwinding on targets that don't support it. I did not find any place where the removed parameter has been used, but it feels a bit risky as I'm new to this test framework. r? bjorn3
Instead of relying on a command line parameter, detect if a target is able to unwind or not. Ignore tests that require unwinding on targets that don't support it.
This test case actually requires std::process.
@bors r+ |
@bors r+ |
Detect panic strategy using `rustc --print cfg` Instead of relying on a command line parameter, detect if a target is able to unwind or not. Ignore tests that require unwinding on targets that don't support it. I did not find any place where the removed parameter has been used, but it feels a bit risky as I'm new to this test framework. r? bjorn3
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#102094 (Add missing documentation for `bool::from_str`) - rust-lang#102115 (Add examples to `bool::then` and `bool::then_some`) - rust-lang#102134 (Detect panic strategy using `rustc --print cfg`) - rust-lang#102137 (Don't convert valtree to constvalue during normalization) - rust-lang#102148 (add regression test for miri issue 2433) - rust-lang#102158 (rustdoc: clean up CSS/DOM for deprecation warnings) - rust-lang#102177 (Fix a typo in `std`'s root docs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#102094 (Add missing documentation for `bool::from_str`) - rust-lang#102115 (Add examples to `bool::then` and `bool::then_some`) - rust-lang#102134 (Detect panic strategy using `rustc --print cfg`) - rust-lang#102137 (Don't convert valtree to constvalue during normalization) - rust-lang#102148 (add regression test for miri issue 2433) - rust-lang#102158 (rustdoc: clean up CSS/DOM for deprecation warnings) - rust-lang#102177 (Fix a typo in `std`'s root docs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…gs, r=Mark-Simulacrum Adding target_rustcflags to `compiletest` TargetCfg creation Adjustment to rust-lang#102134, ensures config returned by `rustc --target foo --print cfg` accurately reflects rustflags passed via `target_rustcflags`. Fixes breaking change of not correctly handling `x.py test ... --test-args "--target-rustcflags -Cpanic=abort --target-rustcflags -Zpanic_abort_tests"` cc `@djkoloski`
…, r=Mark-Simulacrum Adding target_rustcflags to `compiletest` TargetCfg creation Adjustment to rust-lang#102134, ensures config returned by `rustc --target foo --print cfg` accurately reflects rustflags passed via `target_rustcflags`. Fixes breaking change of not correctly handling `x.py test ... --test-args "--target-rustcflags -Cpanic=abort --target-rustcflags -Zpanic_abort_tests"` cc `@djkoloski`
…Simulacrum Adding target_rustcflags to `compiletest` TargetCfg creation Adjustment to rust-lang/rust#102134, ensures config returned by `rustc --target foo --print cfg` accurately reflects rustflags passed via `target_rustcflags`. Fixes breaking change of not correctly handling `x.py test ... --test-args "--target-rustcflags -Cpanic=abort --target-rustcflags -Zpanic_abort_tests"` cc `@djkoloski`
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#102094 (Add missing documentation for `bool::from_str`) - rust-lang#102115 (Add examples to `bool::then` and `bool::then_some`) - rust-lang#102134 (Detect panic strategy using `rustc --print cfg`) - rust-lang#102137 (Don't convert valtree to constvalue during normalization) - rust-lang#102148 (add regression test for miri issue 2433) - rust-lang#102158 (rustdoc: clean up CSS/DOM for deprecation warnings) - rust-lang#102177 (Fix a typo in `std`'s root docs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…Simulacrum Adding target_rustcflags to `compiletest` TargetCfg creation Adjustment to rust-lang/rust#102134, ensures config returned by `rustc --target foo --print cfg` accurately reflects rustflags passed via `target_rustcflags`. Fixes breaking change of not correctly handling `x.py test ... --test-args "--target-rustcflags -Cpanic=abort --target-rustcflags -Zpanic_abort_tests"` cc `@djkoloski`
…Simulacrum Adding target_rustcflags to `compiletest` TargetCfg creation Adjustment to rust-lang/rust#102134, ensures config returned by `rustc --target foo --print cfg` accurately reflects rustflags passed via `target_rustcflags`. Fixes breaking change of not correctly handling `x.py test ... --test-args "--target-rustcflags -Cpanic=abort --target-rustcflags -Zpanic_abort_tests"` cc `@djkoloski`
Instead of relying on a command line parameter, detect if a target is able to unwind or not.
Ignore tests that require unwinding on targets that don't support it.
I did not find any place where the removed parameter has been used, but it feels a bit risky as
I'm new to this test framework.
r? bjorn3