-
Notifications
You must be signed in to change notification settings - Fork 208
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
Codecov responds with "Repository not found" #1623
Comments
@SethMMorton can you try using v4? We are not actively doing work on v3 |
As I mentioned in the original post, I get the same results for both V3 and V4. |
Ah sorry @SethMMorton, can you share the output of v4? |
I re-tried with V4 and it is now working. I'll try to dig through the old logs to find where I used V4 before and it failed, but it seems like maybe the issue was transient. |
@SethMMorton got it, thanks for getting back to me! I'll close for now, but if you run into it again, please feel free to re-open and tag me |
I'm hitting this same problem (3 out of 3 tries so far) - e.g. https://github.com/elalish/manifold/actions/runs/11753759913/job/32747207966?pr=1032
I'm using v4 and I just set up an access token when I realized our codecov hadn't been updated for months due to the access change. I'm not allowed to reopen apparently, but I can tag you as requested, @thomasrockhu-codecov. |
I just retried and it's still failing - doesn't seem transient. I also see that someone else hit the same bug and decided to migrate to coverall in response: raeperd/test.go#6. I'm considering the same if no one can help out here. |
@eliatcodecov I responded on your PR, let me know and I can dig more into why this is happening for you |
Posting the CI build failure to make it easier for me to find: elalish/manifold#1032 |
I am experiencing an inability to upload to
codecov
.I was using v3 without a token, and I was getting the following rejection message:
I then registered a global upload token with Codecov and added that to my configuration, and now the message I get is:
I get this same response whether or not I am using v3 or v4.
How can I solve this "Repository not found" error?
The text was updated successfully, but these errors were encountered: