diff options
| author | bors <bors@rust-lang.org> | 2023-06-13 19:03:27 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-06-13 19:03:27 +0000 |
| commit | 2445d740f741c9d0954822ef0f0cd0c2a1c6acd2 (patch) | |
| tree | bae2f3ff46bbc14158a255e684a1667cba4a4cde /compiler/rustc_interface/src/errors.rs | |
| parent | f8cde5884d94617044c8c40d24f9fe6f355fd73f (diff) | |
| parent | 7886be6327772937d895c9738edb097b06d18b74 (diff) | |
| download | rust-2445d740f741c9d0954822ef0f0cd0c2a1c6acd2.tar.gz rust-2445d740f741c9d0954822ef0f0cd0c2a1c6acd2.zip | |
Auto merge of #112314 - ferrocene:pa-core-alloc-abort, r=bjorn3
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.
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions