diff options
| author | Michael Goulet <michael@errs.io> | 2024-01-05 10:57:20 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-05 10:57:20 -0500 |
| commit | d180e9101dd9cd08ed1f25de5dbab83d7f964e12 (patch) | |
| tree | 30ca778ce110a69d3ab6c248e59f7ea82763c2fd /compiler/rustc_codegen_gcc | |
| parent | 6bc08a725f888a06ea3c6844f3d0cc2d2ebc5142 (diff) | |
| parent | 731ba80a6b53e3397eadeda37b18bd8fb3016aad (diff) | |
| download | rust-d180e9101dd9cd08ed1f25de5dbab83d7f964e12.tar.gz rust-d180e9101dd9cd08ed1f25de5dbab83d7f964e12.zip | |
Rollup merge of #119034 - Zalathar:ignore-mode, r=davidtwco
Allow coverage tests to ignore test modes, and to enable color in coverage reports
This PR adds two new header directives to compiletest, intended for use by coverage tests (and by #119033 in particular).
The new headers are:
- `// ignore-mode-{mode}` causes a test to not be run in a particular compiletest mode (e.g. `ignore-mode-coverage-run`).
- This can theoretically be used by any test, but coverage tests are currently the only ones that automatically run in multiple modes, so it's not very useful for other kinds of test.
- `// llvm-cov-flags: --use-color` makes `coverage-run` tests pass the flag `--use-color` when generating coverage reports.
- For most tests, non-coloured reports are easier to read and more portable across platforms. But for #119033 specifically, we want to test that `llvm-cov` slices up source text correctly, which only happens when colour output is enabled.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions