Codecov upload fails

[bschilder]

Not sure if this is :

• Specific to HPOExplorer
• Related to rworkflows action itself
• Intermittent disruption in codecov service

https://github.com/neurogenomics/HPOExplorer/actions/runs/6786093696/job/18445819354#step:4:1657

Run covr::codecov()
  covr::codecov()
  shell: Rscript {0}
  env:
    RGL_USE_NULL: TRUE
    R_REMOTES_NO_ERRORS_FROM_WARNINGS: true
    RSPM: 
    TZ: UTC
    NOT_CRAN: false
    GITHUB_TOKEN: ***
Request failed [404]. Retrying in 1.4 seconds...
Request failed [404]. Retrying in 3.1 seconds...
$detail
[1] "Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue."

[bschilder]

This seems to be the source of the issue:

• https://community.codecov.com/t/upload-issues-unable-to-locate-build-via-github-actions-api/3954

  We have recently seen an influx in issues regarding uploading with the error message Unable to locate build via Github Actions API. The reason for the failed uploads is due to Codecov’s inability to check the validity of a coverage upload when using tokenless uploads. The underlying issue is rate-limiting from GitHub.

The short-term solution is to have each user add a CODECOV_TOKEN GH secret to each repo. But I really don't like this approach as it's manual and not scalable.

Moving this issue to rworkflows repo.

[bschilder]

I think HPOExplorer/MultiEWCE are especially susceptible to this bc:

• they both make a lot of frequent downloads via piggyback
• i tend to develop/push changes to them in tandem, meaning GH token tends to get a lot of usage at once on GHA.

Simply rerunning the same HPOExplorer GHA job seemed to resolve the issue on its own, confirming that this is an intermittent issue that seems to stem from problems with GH API limits (or at least how codecov interacts with them).

[bschilder]

Will close this for now, but to summarise,

the current solutions are:

• Rerun the action until the codecov works
• Add a repo-specific codecov token as a GH Secret.

In the future, it may be worth looking into using the official action. I probably tried it at some point, so not sure if there's a specific reason why I haven't implemented it already:

• https://github.com/codecov/codecov-action