aboutsummaryrefslogtreecommitdiff
path: root/test cases/failing/67 subproj different versions/subprojects/b/b.c
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2021-07-13 16:43:12 -0400
committerJussi Pakkanen <jpakkane@gmail.com>2021-07-14 19:01:49 +0300
commitc7a0c5cde4284d5c4fdd0bdf249f95144daad5a6 (patch)
treecea126fa04c55f97f8ad9310ab88d21212d88adc /test cases/failing/67 subproj different versions/subprojects/b/b.c
parent762c073500dacd140f66ea04e6d9be554ce77795 (diff)
downloadmeson-c7a0c5cde4284d5c4fdd0bdf249f95144daad5a6.zip
meson-c7a0c5cde4284d5c4fdd0bdf249f95144daad5a6.tar.gz
meson-c7a0c5cde4284d5c4fdd0bdf249f95144daad5a6.tar.bz2
coverage: disable the concept of "CI failures"
code coverage may be interesting to some people as an informational update, but it's really fragile and sometimes obscure, and overall we would really like to NOT have most PRs reporting a red X in the CI overview, when all project/unittests succeeded but codecov decides that by some inscrutbale metric, coverage by % has dropped. Elegant refactorings are penalized, because removing lines of code or rewriting them to be more compact, means the overall percentage of covered code is "less", even though no uncovered code got added. Even worse, the coverage reports often erroneously complain that a PR has "added lines #L<num> - L<num> were not covered by tests" even though github helpfully points out they are "Unchanged files with check annotations". Or more generally, codecov claims that coverage has dropped in code which the PR can't touch. The whole thing is just too much of a source of trouble. So, configure codecov to consider all PRs as successful no matter what. It is still welcome to leave informational comments, though.
Diffstat (limited to 'test cases/failing/67 subproj different versions/subprojects/b/b.c')
0 files changed, 0 insertions, 0 deletions