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 | 371994e0d8380600ddda78ca1be937c7fb179b49 (patch) | |
| tree | d441e6c0baf4b264821e3645f734c35fe768b425 /compiler/rustc_parse/src/parser/expr.rs | |
| parent | 5683791ebb7bbc440366635c322ad82badc554ca (diff) | |
| parent | a988dc2711f033c371fb4b842dc6b436d9cf12ae (diff) | |
| download | rust-371994e0d8380600ddda78ca1be937c7fb179b49.tar.gz rust-371994e0d8380600ddda78ca1be937c7fb179b49.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_parse/src/parser/expr.rs')
0 files changed, 0 insertions, 0 deletions