codecov / codecov/codecov-action

[BUG] Scheduled runs (attempt to) upload to the wrong repository/user

Open
#1,953 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

Describe the bug

For a little while now, we've enabled codecov in kmod although it never quite worked to the fullest.

Namely, continuous data (for the master branch) is not uploaded and/or presented in the UI. Yet data for PRs is uploaded and presented - see (for example)

This could be due to our unusual approach of merging patches manually. In a few odd instances, patches were merged through Github UI and seemingly those have been uploaded/presented in the UI.

To handle the manual merges (+ cases where compiler/coverage tools/etc are updated leading to different results), we have scheduled codecov runs. Those runs should, in theory:

  • upload the results to the correct place repository
  • allow continuous results are presented in the UI

Tl:Dr:

PR uploads correctly end up in "https://app.codecov.io/github/kmod-project/kmod/..."
Schedule runs incorrectly upload to "https://app.codecov.io/github/lucasdemarchi/kmod/..."

To Reproduce
Steps to reproduce the behavior:

  1. Go to a scheduled job
  2. Click on "Upload coverage"
  3. Scroll down to "Your upload is now queued for processing. When finished, results will be available at: "
  4. Observe the incorrect project/user "https://app.codecov.io/github/lucasdemarchi/kmod/commit/..."

Expected behavior

  1. Scheduled jobs behave like the PR ones uploading to the correct project/user.
  2. The UI picks those results and displays them

Regression
This behaviour is observed since we started using codecov in Nov 2024.

Screenshots
Should be self explanatory. Happy to provide some, if you need any.

Product Area
Not sure to be honest...

Versions

  • OS: linux (we're not using macos/windows so not sure if those are affected)
  • Git Host: GitHub
  • CI/CD: GitHub Actions
  • Uploader: codecov-action@v6.0.0

Commit and CI link
See links in description and reproducer sections

Additional context
It's possible that something isn't setup quite right in the kmod repo. The maintainer @lucasdemarchi has access and help assist on that front.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked scheduled GitHub Actions job and inspect the codecov-action@v6.0.0 upload configuration, then compare it with a PR upload that reaches the kmod-project/kmod repository. Done means scheduled runs upload to the correct repository and their coverage appears in the Codecov UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.