-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Ignore core, alloc and test tests that require unwinding on -C panic=abort
#112314
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
Conversation
|
(rustbot has picked a reviewer for you, use r? to override) |
a3c64de to
0aacdaa
Compare
core and alloc tests that require unwinding on -C panic=abortcore, alloc and test tests that require unwinding on -C panic=abort
|
Also added attributes to the |
|
Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 |
|
Removed the ignored tests from the patch. r? @bjorn3 |
9ca495d to
a988dc2
Compare
|
@bors r+ |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (371994e): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 648.13s -> 647.349s (-0.12%) |
Ignore `core`, `alloc` and `test` tests that require unwinding on `-C panic=abort` Some of the tests for `core` and `alloc` require unwinding through their use of `catch_unwind`. These tests fail when testing using `-C panic=abort` (in my case through a target without unwinding support, and `-Z panic-abort-tests`), while they should be ignored as they don't indicate a failure. This PR marks all of these tests with this attribute: ```rust #[cfg_attr(not(panic = "unwind"), ignore = "test requires unwinding support")] ``` I'm not aware of a way to test this on rust-lang/rust's CI, as we don't test any target with `-C panic=abort`, but I tested this locally on a Ferrocene target and it does indeed make the test suite pass.
Some of the tests for
coreandallocrequire unwinding through their use ofcatch_unwind. These tests fail when testing using-C panic=abort(in my case through a target without unwinding support, and-Z panic-abort-tests), while they should be ignored as they don't indicate a failure.This PR marks all of these tests with this attribute:
#[cfg_attr(not(panic = "unwind"), ignore = "test requires unwinding support")]I'm not aware of a way to test this on rust-lang/rust's CI, as we don't test any target with
-C panic=abort, but I tested this locally on a Ferrocene target and it does indeed make the test suite pass.