Resolve all warnings in run-coverage
tests
When one of these tests fails, any compiler warnings will be printed to the console, which makes it harder to track down the actual reason for failure. (The outstanding warnings were found by temporarily adding `-Dwarnings` to the compiler arguments for `RunCoverage` in `src/tools/compiletest/src/runtest.rs`.)
This commit is contained in:
parent
9334ec9354
commit
72b721f48e
20 changed files with 22 additions and 20 deletions
|
@ -1,3 +1,5 @@
|
|||
LL| |#![allow(dead_code, unreachable_code)]
|
||||
LL| |
|
||||
LL| |// Regression test for #93054: Functions using uninhabited types often only have a single,
|
||||
LL| |// unreachable basic block which doesn't get instrumented. This should not cause llvm-cov to fail.
|
||||
LL| |// Since these kinds functions can't be invoked anyway, it's ok to not have coverage data for them.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue