-
Notifications
You must be signed in to change notification settings - Fork 221
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
Unable to locate build via Github Actions API #903
Comments
You need to use the action with a token despite what the documentation says (that it's only the case for private repos). We used to have this problem and builds would generally pass if you re-ran them. With tokens we haven't seen this error. |
Thanks, will try this. If this is true, someone should either fix the documentation or fix the bug that makes it required. It works 95% of the time for us, but that 5% is really frustrating. |
Unfortunately this doesn't seem to help, I'm still seeing the same error even with this token: |
I am also seeing this error from time to time. It tends to happen a lot for some time, and then not happen for a few weeks before reappearing. I do not use the token, but I have tested with and without the token when the issue appears, and neither works. |
@adamjstewart looking at your logs you've shared it doesn't seem you are using a token..
|
And yet I am. microsoft/torchgeo#1077 was merged into main 3 weeks ago. microsoft/torchgeo#1109 was automatically created by dependabot and branched off of main 1 week ago. Is it possible that PRs opened by external collaborators do not have access to secrets? If so, then the "just add a token" fix is no longer a fix. |
Hmm the blurb from the repo settings > secrets page says: "Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork." |
Gotcha, so secrets aren't particularly useful for open source projects. So we should figure out why tokens are necessary (sometimes) to upload coverage reports. |
Closing this in favor of codecov/feedback#126 |
We've been seeing intermittent upload failures recently that have caused problems with coverage reporting. The full error log looks like:
Examples of this behavior include:
The text was updated successfully, but these errors were encountered: