Should I worry about a failure in "Publish code coverage results"?

I have a fork of the cpython repo I try to keep more-or-less up-to-date. The past couple times I’ve synced I’ve gotten an odd failure. The tests with coverage all pass. Should failure to publish coverage results be a concern? Also, is there a better place to ask these questions about the whole GitHub/CI infrastructure?

  1. Run ./.venv/bin/python -m coverage xml
  2. ./.venv/bin/python -m coverage xml
  3. bash <(curl -s
  4. shell: /bin/bash -e {0}
  5. env:
  6. OPENSSL_VER: 1.1.1d
  8. No data to report.
  9. ##[error]Process completed with exit code 1.



This is caused by major update of the coverage.
The issue is already filed.


This is now fixed in 5.0.2.

1 Like