diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-01-19 08:15:04 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-19 08:15:04 +0100 |
| commit | 987445cd42f1235c7599db9752f693459de31330 (patch) | |
| tree | 7883e5910950e56c8724e788a008ee76308ad520 /compiler/rustc_codegen_gcc | |
| parent | 48ba7217c642126b1be18c52a5e3a6a912b5e80c (diff) | |
| parent | 0373ce6876864a2f31b0ab885c7ba80e1f69eb15 (diff) | |
| download | rust-987445cd42f1235c7599db9752f693459de31330.tar.gz rust-987445cd42f1235c7599db9752f693459de31330.zip | |
Rollup merge of #120083 - Zalathar:no-profiler, r=wesleywiser
Warn when not having a profiler runtime means that coverage tests won't be run/blessed On a few occasions (e.g. #118036, #119984) people have been tripped up by the fact that half of the coverage test suite is skipped by default, because it `// needs-profiler-support` and the profiler runtime is not actually built in any of the default config profiles. (This is made worse by the fact that it isn't enabled in any of the PR CI jobs either. So people think that they've successfully blessed the test suite, and then get a rude surprise when their merge only fails in the full CI job suite.) This PR adds a simple warning to compiletest that should alert the user in some cases. It's not foolproof, but it should increase the chances of catching this problem earlier in the PR process.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions