GitHub PR not being updated with final coverage data

Support Bug Fixes
44

@tom I don’t know what exactly fixed it, but I added your suggestions to the config file and removed buildkite. Old PRs still don’t get any coverage report after a force push for some reason, but at least the new ones do.

Because of these issues, we got around to testing the new github actions codecov uploader, however it does not seem to work correctly.
In the CI logs everything looks OK, the paths look fine, it seems to find the secret token, and it says it uploads. But codecov.io claims there were errors processing the reports.
Switch to using Codecov GitHub Action. by nmoinvaz · Pull Request #1158 · zlib-ng/zlib-ng · GitHub

There might be an erronous \n at the end of paths? But I am not sure whether that is an actual error or not, and I don’t think that is something we have control over at all. See: Switch to using Codecov GitHub Action. by nmoinvaz · Pull Request #1158 · zlib-ng/zlib-ng · GitHub

45

@Dead2 (and @nmoinvaz)

It actually looks like a report timing thing. From our side, they have already expired (12 hour time limit). I’m not sure if that is true, or just a time zone issue, but the workaround is

codecov:
  max_report_age: off