CodeCov website shows "There's been an error" when showing coverage on master branch

Before submitting a topic, please confirm the following

I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my codecov.yaml configuration file.
I have filled out the below sections to the best of my ability.
I understand that the community boards are a free, best-effort tool. While we hope to have someone on the Codecov team resolve your problem quickly, this is not always possible.

Description

The CodeCov website returns an error when I click a directory in the file list:
https://app.codecov.io/gh/shap/shap/tree/master/shap

Shows an error:

There's been an error. Please try refreshing your browser, if this error persists please contact support

I’ve tried refreshing the browser, and waiting 24 hours and trying again.

CodeCov seems to be working reasonably well otherwise: for example, the coverage reports are showing up fine for PRs. The home page renders ok:

https://app.codecov.io/gh/shap/shap

CI/CD URL

Example recent run for the master branch:

Codecov Output

==> linux OS detected
https://uploader.codecov.io/latest/linux/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (0c9b79119b0d8dbe7aaf460dc3bd7c3094ceda06e5ae32b0d11a8ff56e2cc5c5  codecov)
==> Running version latest
==> Running version v0.6.1
/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov -n  -Q github-action-3.1.4
[2023-07-21T17:55:08.133Z] ['info'] 
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.6.1
[2023-07-21T17:55:08.145Z] ['info'] => Project root located at: /home/runner/work/shap/shap
[2023-07-21T17:55:08.150Z] ['info'] -> No token specified or token is empty
[2023-07-21T17:55:08.298Z] ['info'] Running coverage xml...
[2023-07-21T17:55:09.612Z] ['info'] Searching for coverage files...
[2023-07-21T17:55:09.681Z] ['info'] Warning: Some files located via search were excluded from upload.
[2023-07-21T17:55:09.681Z] ['info'] If Codecov did not locate your files, please review https://docs.codecov.com/docs/supported-report-formats
[2023-07-21T17:55:09.682Z] ['info'] => Found 1 possible coverage files:
  coverage.xml
[2023-07-21T17:55:09.682Z] ['info'] Processing /home/runner/work/shap/shap/coverage.xml...
[2023-07-21T17:55:09.694Z] ['info'] Detected GitHub Actions as the CI provider.
[2023-07-21T17:55:10.307Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.6.1&token=*******&branch=master&build=5625063447&build_url=https%3A%2F%2Fgithub.com%2Fshap%2Fshap%2Factions%2Fruns%2F5625063447&commit=ae0b9867c1e01f642d57e764bdd47d25ae5892bb&job=tests&pr=&service=github-actions&slug=shap%2Fshap&name=&tag=&flags=&parent=
[2023-07-21T17:55:10.668Z] ['info'] https://app.codecov.io/github/shap/shap/commit/ae0b9867c1e01f642d57e764bdd47d25ae5892bb
https://storage.googleapis.com/codecov/v4/raw/2023-07-21/15CD8AF3EEB03BE8EFAF5733A05997FF/ae0b9867c1e01f642d57e764bdd47d25ae5892bb/a07cbe48-e00c-44a3-ab38-bf1d6404e77c.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EJOGFN2JQ4OCTGA2MU5AEIT7OT5Z7HTFOAN2SPG4NWSN2UJYOY5U6LZQ%2F20230721%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20230721T175510Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=d284f61e6973566e0a1935a2260c84c9b7e827dd77dff4fb948aa17fecbd03ef
[2023-07-21T17:55:10.669Z] ['info'] Uploading...
[2023-07-21T17:55:10.867Z] ['info'] {"status":"success","resultURL":"https://app.codecov.io/github/shap/shap/commit/ae0b9867c1e01f642d57e764bdd47d25ae5892bb"}

Additional Information

One recent change is that the repository was migrated on GitHub from a user namespace https://github.com/slundberg/shap/ to an org namespace, https://github.com/shap/shap/ . I have ensured that the CodeCov OAuth app has been given permissions in the new org.

@connor1 I’m not sure if this issue was a result, but I’m seeing no errors now. Is this still an issue for you?

It seems to be working today - perhaps the issue you linked was the cause. Thanks anyway

1 Like