diff options
| author | bors <bors@rust-lang.org> | 2023-07-09 21:37:56 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-07-09 21:37:56 +0000 |
| commit | 70d7283d24ed2d664fc4cefad6f240aeb62e98f2 (patch) | |
| tree | 61afdcaa3766cef7a73dffdb8d5c3a6494edf5b3 /compiler/rustc_codegen_cranelift/example/alloc_example.rs | |
| parent | 1065d876cdbc34a872b9e17c78caaa59ea0c94d4 (diff) | |
| parent | e4b81f6d71ba3d9823b0133a985e8d0c77dfe2f3 (diff) | |
| download | rust-70d7283d24ed2d664fc4cefad6f240aeb62e98f2.tar.gz rust-70d7283d24ed2d664fc4cefad6f240aeb62e98f2.zip | |
Auto merge of #113389 - Zalathar:re-enable, r=Mark-Simulacrum
Re-enable some coverage tests on Linux These tests were originally disabled (on all platforms) in #110393, because those changes had made them start failing on Linux for unclear reasons. I tried to re-enable them unconditionally in #111179, since they worked locally on my Mac, but I found that they were still failing on Linux, so I gave up at that time. Later while working on #112300 I was able to re-enable them on Windows and Mac, since those changes made it possible to add specific `ignore-` directives to individual tests. I noticed at the time that the tests actually seemed to be working again on Linux, but by that point I didn't want to risk more CI failures, so I left them disabled on Linux with an intention to re-enable them later. Now I'm going back to re-enable them on Linux too, since they seem to work fine. --- Because `run-coverage` tests are sensitive to line numbers, and `x test tidy` doesn't like leading blank lines, I've replaced the old comment/ignore with an informative comment that occupies the same number of lines.
Diffstat (limited to 'compiler/rustc_codegen_cranelift/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions
