Closed kdarkhan closed 4 months ago
Hey @kdarkhan, I would suggest moving to the simplest setup: only generate covera reports after merges. That should work fine: it will allow us to use the privileged trigger from the main
branch.
We will still get the history of coverage over time on main
and we can then look at this to determine where we have big holes in our test coverage.
@mgeisler, that can be done and it will simplify commit/PR detection logic I defined in the pipelines.
It will probably not resolve this specific issue as the bug is in the new version of codecov action. v3 version works pretty stable and v4 should be fixed eventually since there are many complaints from users on the breakage.
Removing PR comments/analysis can be done if you think they are distracting but not because of this upgrade failure.
Removing PR comments/analysis can be done if you think they are distracting but not because of this upgrade failure.
Ah, I see! Then I think we should just keep things the way they are now. As you say, the issue will probably be fixed eventually.
Coverage reports started failing after upgrade from v3 to v4.
Example failure here
Error message