Closed lbianchi-lbl closed 1 week ago
I think I'm seeing this same issue at https://github.com/lmfit/uncertainties/pull/269. The seems to be related to the PR coming from a forked repo and using tokenless uploading. If I include the token explicitly (instead of as a secret), I've found this error message to go away and the github action job to succeed. However, the coverage reports don't actually appear on codecov.io. I'm confused.
Hi @jagerber48 Can you share the SHA for the one that "worked", but isn't showing on Codecov? Can you also check the uploader output and make sure it was uploaded under the same SHA you expected?
@drazisil-codecov what SHA do you mean? https://app.codecov.io/gh/lmfit/uncertainties/commit/332898b6259474896a6d55504623dde3e948e688 here's the codecov page for the last commit that got an upload to appear on codecov.io and this is the github action run https://github.com/lmfit/uncertainties/actions/runs/11812705246/job/32908343823.
The other jobs in that same workflow all have the failed message under discussion in this issue (I think).
Same issue here:
Linux (https://github.com/mozilla/neqo/actions/runs/11839045971/job/32989585647#step:9:106) and Windows (https://github.com/mozilla/neqo/actions/runs/11839045971/job/32989588896#step:9:152) failing, MacOS still succeeds (https://github.com/mozilla/neqo/actions/runs/11839045971/job/32989587215#step:9:97).
Hi @jagerber48 I was referring to this:
If I include the token explicitly (instead of as a secret), I've found this error message to go away and the github action job to succeed. However, the coverage reports don't actually appear on codecov.io.
@larseggert Why does it look like the two failing ones are tryingto upload to https://errors.pydantic.dev/2.4/v/missing
, instead of Codecov? Am I missing where you are setting an env or override somewhere?
I don't think so? Haven't touched the CodeCov CI pipeline in a while.
Not an expert on what this output means; to me it looked like the pydantic stuff was an error coming back from CodeCov?
@jagerber48 Your failure looks a lot of https://github.com/codecov/engineering-team/issues/2882. I hope to have a chance to dig into that today, but my fellow support engineer is on vacation, so it's been hectic.
Not an expert on what this output means; to me it looked like the pydantic stuff was an error coming back from CodeCov?
It did, but I think that's became the CLI was being told that was the upload URL. Can you enable verbose for me please?
Linux debug run: https://github.com/mozilla/neqo/actions/runs/11839045971/job/32991914319#step:9:153 MacOS debug run: https://github.com/mozilla/neqo/actions/runs/11839045971/job/32991915533#step:9:144 Windows debug run: https://github.com/mozilla/neqo/actions/runs/11839045971/job/32991916742#step:9:199
@larseggert Ah, I meant setting verbose: true
for the action, sorry. I need it to make more logs π
It has
verbose: true
? https://github.com/mozilla/neqo/blob/68e19fc0ae9c906cf98c2a501b95f38e7fc4a7b9/.github/workflows/check.yml#L119
Sorry, I saw the debug logs from GitHub and stopped reading π€¦ββ
I think we know what's going on here, and I'm trying to follow the internal Slack thread. For now, I think using the token will fix it, but I expect a fix version soon.
How do I use the token from a fork?
How do I use the token from a fork?
Ugg. You can't. Checking on the fix...
@larseggert Why does it look like the two failing ones are tryingto upload to
https://errors.pydantic.dev/2.4/v/missing
, instead of Codecov? Am I missing where you are setting an env or override somewhere?
Not sure if this matters, but it looks like the https://errors.pydantic.dev
URL is part of the default error message emitted when the Pydantic validation fails (in this specific case, signaling that the field id
is missing, i.e. required in the model definition, but not present in the input
dict that's being parsed): https://docs.pydantic.dev/2.4/#pydantic-examples
Thank you both! https://github.com/codecov/shelter/pull/222 should fix this error, once merged
Thank you both! https://github.com/codecov/shelter/pull/222 should fix this error, once merged
Thanks a lot for looking into this! It looks like I can't access that link (private repository?). Could you notify us here once it happens so we can try to re-run the upload jobs and see if the issue is resolved?
oh! π€¦ββ
I forgot that repo isn't ready for source available yet. It's merged now and it's Google Cloudrun.... so it's probably a very fast deploy? π€
oh! π€¦ββ
I forgot that repo isn't ready for source available yet. It's merged now and it's Google Cloudrun.... so it's probably a very fast deploy? π€
Not yet, sorry.
Gah. I forgot to come back. It should be good now.
It looks like our Codecov report upload jobs are now passing, without any changes needed on our side:
Thanks again for looking into this. As far as I'm concerned this fully resolves my original issue, but I'll defer the decision to close the issue to you in case you want to get more feedback from the other commenters.
Seems to be working on our end as well, thank you!
Describe the bug
Report upload using
codecov/codecov-action@v4
on a PR fails with a 202 error code:Environment (please complete the following information):
Environment: GitHub Actions (
codecov/codecov-action@v4
)Runner information:
codecov/codecov-action@v4
configuration:https://github.com/watertap-org/watertap/blob/532ce63868ca0dc949731866a7caa4e9d8c468ac/.github/workflows/checks.yml#L163-L172
To Reproduce
Use
codecov/codecov-action@v4
in a GitHub Actions workflow (triggered by apull_request
event) for a public repositoryExpected behavior The upload process completes successfully
Screenshots
Additional context Add any other context about the problem here.