You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reasons instead of comparing against the latest main (or at least v5.0.0), codecov is pinned to 60e928f (example 1, example 2).
The codecov bot prematurely writes the comment (before all the tests are run on all platforms) and only later edits it, and triggers transient false alarms for coverage failure.
There are duplicate/empty Codecov Upload job steps in the build_binpy_wheels job (example):
The first one is skipped because ${{ secrets.CODECOV_TOKEN }} is undefined.
The second one reports that no coverage files are found (because cibuildwheel doesn't doesn't run pytest with coverage) and that it thus Failed to run upload-coverage. (This however doesn't cause the pipeline to fail.)
main(or at leastv5.0.0),codecovis pinned to 60e928f (example 1, example 2).codecovbot prematurely writes the comment (before all the tests are run on all platforms) and only later edits it, and triggers transient false alarms for coverage failure.Codecov Uploadjob steps in thebuild_binpy_wheelsjob (example):${{ secrets.CODECOV_TOKEN }}is undefined.cibuildwheeldoesn't doesn't runpytestwithcoverage) and that it thusFailed to run upload-coverage. (This however doesn't cause the pipeline to fail.)codecov-actionfails (we can use thefail_ci_if_errorswitch for that)?Codecov Uploadjob step issues a warning because thefileparameter has been superseded byfiles.