-
Notifications
You must be signed in to change notification settings - Fork 243
Description
Describe the bug
This is an escalation from Zendesk. PII has been redacted.
We have been experiencing the issue codecov/patchExpected — Waiting for status to be reported for a while now.
I tried adding verbose to the Codecov uploader, and I’m seeing this:
debug - 2025-12-31 11:30:17,337 -- Sending upload request to Codecov
info - 2025-12-31 11:30:17,764 -- Your upload is now processing. When finished, results will be available at: https://app.codecov.io/github/***/***/commit/***
debug - 2025-12-31 11:30:17,764 -- Upload request to Codecov complete. --- {"response": {"raw_upload_location": "***", "url": "***"}}
debug - 2025-12-31 11:30:17,765 -- Sending upload (578792 bytes) to storage
info - 2025-12-31 11:30:18,335 -- Process Upload complete
debug - 2025-12-31 11:30:18,335 -- Upload result --- {"result": "RequestResult(error=None, warnings=[], status_code=200, text='')"}To Reproduce
This is the part of our pull_request.yml in which we send the data to codecov
test:
#
# ensure tests pass
#
runs-on: ubuntu-latest
permissions:
contents: read
actions: read
checks: write
steps:
# Checkout code to test.
- name: Checkout repo
uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
cache: 'npm'
- run: npm ci
- name: unittest
run: npm run test:ci
- name: Upload test results to Codecov
if: ${{ !cancelled() }}
uses: codecov/test-results-action@v1
with:
fail_ci_if_error: true
files: ./junit.xml
token: ${{ secrets.CODECOV_TOKEN }}
- name: Upload test coverage results to Codecov
uses: codecov/codecov-action@v4
with:
token: ${{ secrets.CODECOV_TOKEN }}
files: ./coverage/lcov.info,./coverage/clover.xml
verbose: true
fail_ci_if_error: trueI understand that the file was successfully uploaded; however, GitHub is still waiting for Codecov’s status.
We had this problem in a repo in golang before, and we could fix it after adding some positive paths in our codecov.yaml, but this time we did the same and is not working. We are probably missing something on this vue project.
We tried using the codecov/codecov-action@v5 version; unfortunately, this issue has been going on for more than two weeks and we haven’t been able to find the root cause. This used to work before, and we hadn’t made any changes, but for some reason it stopped working.
We decided to add the following change to our codecov.yaml:
codecov:
notify:
wait_for_ci: false
require_ci_to_pass: falseAfter that, we reverted to v4 (we had also tried v5 and it didn’t work either), and with this change in the YAML we were able to merge an urgently needed task into main.
Additional context
https://sentry.zendesk.com/agent/tickets/170990