actions / actions/upload-code-coverage
Coverage upload failed (HTTP 404)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 99
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Running actions/upload-code-coverage fails with the following error message:
Error: Coverage upload failed (HTTP 404): Not Found. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Error: Process completed with exit code 1.
The action is configured as such:
- name: upload coverage report
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
uses: actions/upload-code-coverage@v1
with:
file: coverage/coverage.xml
language: ruby
label: coverage
And these are the recognized parameters the action runs with:
commit_oid: 578fc6d9cad30bcc31100837764e1fc08b50ad11
ref: refs/heads/remove-codecov
pr_number: 256
language: ruby
label: coverage
file: coverage/coverage.xml (8687 bytes)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the actions/upload-code-coverage@v1 workflow step with coverage/coverage.xml and the listed commit, ref, pull request, language, and label parameters. Trace the HTTP 404 response and compare it with the action's expected upload inputs. Done means the Ruby coverage report uploads successfully without the workflow failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python, ruby
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100