We did this because Codecov was reporting a failing status check for the protocol project seemingly randomly.
Specifically, the protocol test coverage is only uploaded daily. That’s why we initially added if_not_found: success to its config.
However we saw that - randomly - the status check for the protocol project would report an error with 0.00% (target 90.00%) instead of the expected success status with No files found while filtering the report.
Today, Feb 27, we see Codecov is still reporting the failing status check for the removed protocol project (also seemingly randomly).
It looks like Codecov isn’t fully taking our updated config file into account.
Repository
Steps to Reproduce
Have multiple projects in your Codecov config
See statuses being reported to GitHub
Delete one project from the config
See Codecov reporting status for the deleted project even when no coverage was uploaded for it
Expected behavior:
Codecov should not report failing status for a deleted project.
Codecov should consistently report a success status with No files found while filtering the report. when not uploading coverage and if_not_found: success is set for a project.
Actual behavior:
Codecov is reporting failing status for a deleted project even when not uploading any coverage for it.
Codecov is reporting an error status with 0.00% (target 90.00%) instead of success status with No files found while filtering the report. when not uploading coverage and if_not_found: success is set for a project.
Commenting out a status will disable that status, it won’t tell Codecov to stop processing those files. I recommend adding that path to your ignore section if you want us to not handle it.
I’m confused about your answer.
The screenshot above shows Codecov still reporting the status for the project that has been commented out in the config. And you’re saying it shouldn’t, right?
Also, as far as I saw, we did not upload anything related to that path when that status in the screenshot was reported.
Next step, disabling statuses for codecov/patch and codecov/project.
From what I see, Codecov online validator still reports the same valid output though (curl --data-binary @codecov.yml https://codecov.io/validate).
Could you explain why those changes are necessary given the validator indicates they are the same?
Yes, the validate endpoint currently points to the old validator, not the stricter, schema-driven one the processor uses. This make it only 97% accurate currently, but this is on track to be fixed soon.
I think patch: off (drop the default part) should work. Still thinking on why the default project status is showing, let me check the logs.
Hi @jeanregisser, I’m a bit out of the loop on this issue, and I just wanted to see if I could give you an update here, but I’m not sure what state your projects are currently in. Are you still experiencing an issue with this, and if so, how can I help?