Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GHA v4 does not work well when run from workflow_run instead of pull_request #273

Closed
1 task done
rohan-at-sentry opened this issue Feb 13, 2024 · 11 comments
Closed
1 task done
Assignees
Labels
Area: Report Upload Issues with pre-ingest report uploading bug For issues and unexpected behaviors Low Low Priority Issues (to be fixed or re-evaluated in 12 months

Comments

@rohan-at-sentry
Copy link

rohan-at-sentry commented Feb 13, 2024

#126 (comment)

Related issues

@covecod covecod bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 Feb 13, 2024
@rohan-at-sentry rohan-at-sentry added bug For issues and unexpected behaviors and removed Waiting for: Product Owner labels Feb 13, 2024
@covecod covecod bot removed the status in GitHub Issues with 👀 Feb 13, 2024
@rohan-at-sentry
Copy link
Author

@thomasrockhu-codecov can you take a look at this once you're back in?

@covecod covecod bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 Feb 13, 2024
JoshuaKGoldberg added a commit to JoshuaKGoldberg/create-typescript-app that referenced this issue Feb 14, 2024
## PR Checklist

- [x] Addresses an existing open issue: fixes #1303
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

codecov/codecov-action#1292 &
codecov/feedback#273 make me not want to deal
with this token stuff until it's all resolved.

Things were working fine before, and I really don't want to add a
_third_ token requirement to repos made with `create-typescript-app`.
@thomasrockhu-codecov
Copy link
Contributor

Ok, I did a run on a workflow_run event and it seems to be working fine. See this run.

This leads me to believe there is something else happening. @kdarkhan @adamjstewart @melink14 @JoshuaKGoldberg, if you have any logs or a link that you could point me to, I'd be happy to look in and see why the action@v4 is not working

@JoshuaKGoldberg
Copy link

Thanks for asking! All of my repos that use the Codecov action should be open source. JoshuaKGoldberg/create-typescript-app#1289 -> JoshuaKGoldberg/create-typescript-app#1303 -> JoshuaKGoldberg/create-typescript-app#1304 should be the main references for that repository in particular. If there's any logstuffs you don't have access to, I'd be happy to provide them.

That repo also is a GitHub repo template you can use to make a new repo to test for yourself. LMK if that's not clear how to use here either 🙂

@thomasrockhu-codecov
Copy link
Contributor

@JoshuaKGoldberg

You need to add the token as a secret and as an argument to the codecov-action step from the message on this log

@adamjstewart
Copy link

Ok, I did a run on a workflow_run event and it seems to be working fine. See this run.

Uh, from what I can tell, this was triggered by thomasrockhu-codecov/example-python#1, which is not from a fork. Also, the "Download coverage artifacts" step failed to find and download anything. Therefore I would be pretty surprised if the "Upload coverage to codecov" step was doing anything useful. In my testing, I was able to get both of those steps working correctly. The issue I encountered was that workflow_run never reported back to the original PR that triggered it, so PRs like microsoft/torchgeo#1868 never received any coverage information.

@thomasrockhu-codecov
Copy link
Contributor

@adamjstewart got it, is this specifically in PRs from forks only then?

@adamjstewart
Copy link

I guess I've never tried a PR from upstream since we don't usually get any out those for open source repos.

@thomasrockhu-codecov
Copy link
Contributor

got it, @adamjstewart I'm not sure this is a specific workflow_run thing, but I'll dig into the logs to see what happened, and why you didn't get a status check or comment. To be clear, I'm going to use this PR as #1868 doesn't seem to have been run at all. Let me know if I misunderstood something.

@thomasrockhu-codecov
Copy link
Contributor

@adamjstewart I see the problem, the issue was due to rate limiting. Have you installed the Codecov app on your fork?

@adamjstewart
Copy link

@thomasrockhu-codecov the rate limiting issue was the reason for opening #126. The reason we're using workflow_run is to try to get around the rate limiting issue. We can't expect all of our contributors to first install the Codecov app in order to get their PRs to pass the tests.

@thomasrockhu-codecov thomasrockhu-codecov added the High High Priority Issues (to be fixed within 2 sprints) label Oct 29, 2024
@thomasrockhu-codecov thomasrockhu-codecov added Low Low Priority Issues (to be fixed or re-evaluated in 12 months and removed High High Priority Issues (to be fixed within 2 sprints) labels Oct 29, 2024
@thomasrockhu-codecov thomasrockhu-codecov added the Area: Report Upload Issues with pre-ingest report uploading label Oct 29, 2024
@thomasrockhu-codecov
Copy link
Contributor

@adamjstewart I'm going to close this as I believe it's been fixed. However, if you feel that isn't true, please feel free to create a new issue and tag me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Report Upload Issues with pre-ingest report uploading bug For issues and unexpected behaviors Low Low Priority Issues (to be fixed or re-evaluated in 12 months
Projects
Status: Waiting for: Product Owner
Development

No branches or pull requests

4 participants