How to measure and diagnose performance issues when uploading coverage reports with Codecov GitHub Action?

Likely explanation

Performance issues when uploading coverage reports with the Codecov GitHub Action are often related to the size of the report, network latency between the runner and Codecov’s endpoint, or the amount of debugging information being logged. These factors can increase upload time and appear as slow job steps.

Confirmed facts

No specific information about Codecov upload performance is present in the supplied sources, so there are no confirmed facts to cite.

Steps to measure and diagnose

1. Enable verbose logging for the Codecov action by setting the environment variable CODECOV_DEBUG=true in your workflow.
2. Wrap the upload step with a timing command, for example:

       - name: Upload coverage
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
           CODECOV_DEBUG: true
         run: |
           time -p bash -c 'codecov'

   This will output real‑time, user‑time and sys‑time for the upload command.
3. Check the size of the coverage artifact before upload. You can add a step that prints the file size:

       - name: Show coverage size
         run: du -h path/to/coverage.xml

4. Review the action’s output for any retry messages or network‑related warnings; the debug log will show HTTP request timings and response codes.
5. If the upload is consistently slow, compare the timing with a simple curl test to the Codecov endpoint from the same runner to isolate network latency:

    - name: Network latency test
      run: time -p curl -o /dev/null -s -w '%{time_total}\n' https://codecov.io/upload/v4

What to ask next

To refine the recommendation, please confirm the approximate size of the coverage report you are uploading (e.g., a few kilobytes, several megabytes, or larger). This detail determines whether compression or report trimming would be effective.