Description
While creating a new pull request several times, it happens that the codecov has reported negative coverage for files that have not been modified at all. It also varies, sometimes codecov is positive and sometimes is not.
Here is a PR link (Added JUnit tests for ValueTokenizer class by code-incubus · Pull Request #2937 · eclipse/kapua · GitHub), it is an open-source project.
After creating the PR on eclipse / kapua official repo, codecov generates negative coverage. Meanwhile, I tried to do the same PR to my forked develop and there codecov works without problems (https://github.com/code-incubus/kapua/pull/3).
The question is why codecov generate and show negative reports / or missed lines. if the new tests were added and if the CI passed correctly?
Please advise for any hint regarding this issue.
Repository
My forked project:
https://github.com/code-incubus/kapua
Official repo:
Versions
/
Additional Information
I am also submitting a .yaml file configuration …
codecov:
require_ci_to_pass: true
comment:
behavior: default
layout: "reach, diff, flags, files"
require_base: false
require_changes: false
require_head: true
coverage:
precision: 2
range: "70...100"
round: down
status:
changes: false
project: true
patch: true
parsers:
gcov:
branch_detection:
conditional: true
loop: true
method: false
macro: false
javascript:
enable_partials: false
ignore:
- "qa"
- "**/test/"
- "**/test-steps/"