a0b925dae3
We run tests for more python versions on `develop` than we do for PRs, so codecov project status is nearly always failing. There is about a 1% difference in max coverage between `develop` tests and PR tests, so we should increase the project threshold to 2% to allow for this difference. The purpose of the project test on PRs is just to make sure that nothing done on the PR massively affects coverage of code not covered by the PR. This is valuable, but rare. It only really affects PRs that deal with test or coverage configuration. - [x] change project coverage threshold from .2% to 2% Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
35 lines
963 B
YAML
35 lines
963 B
YAML
coverage:
|
|
precision: 2
|
|
round: nearest
|
|
range: 60...90
|
|
status:
|
|
project:
|
|
default:
|
|
threshold: 2.0%
|
|
|
|
ignore:
|
|
- lib/spack/spack/test/.*
|
|
- lib/spack/docs/.*
|
|
- lib/spack/external/.*
|
|
- share/spack/qa/.*
|
|
|
|
comment: off
|
|
|
|
# Inline codecov annotations make the code hard to read, and they add
|
|
# annotations in files that seemingly have nothing to do with the PR.
|
|
github_checks:
|
|
annotations: false
|
|
|
|
# Attempt to fix "Missing base commit" messages in the codecov UI.
|
|
# Because we do not run full tests on package PRs, package PRs' merge
|
|
# commits on `develop` don't have coverage info. It appears that
|
|
# codecov will give you an error if the pseudo-base's coverage data
|
|
# doesn't all apply properly to the real PR base.
|
|
#
|
|
# See here for docs:
|
|
# https://docs.codecov.com/docs/comparing-commits#pseudo-comparison
|
|
# See here for another potential solution:
|
|
# https://community.codecov.com/t/2480/15
|
|
codecov:
|
|
allow_coverage_offsets: true
|