@drazisil I am using the bash uploader. It’s a step in my CI set up in Azure DevOps pipeline.
This is the command used
bash <(curl -s https://codecov.io/bash) -t ${token}
OK, you can change it to bash <(curl -s https://codecov.io/bash) -t ${token} -d to view the report that would be uploaded, but keep in mind you would need to run it a second time without the -d flag if you want to upload to Codecov also. I have attached your ticket to our investigation regarding the stuck reports.
That’s annoying. Can you try adjusting your codecov.yml to change the behavior to either new or update, to see if that fixes the duplicate comments? Pull Request Comments
@drazisil Sure, I can do that. A little confused how it is posting as both the web hook and app are both down.
Looks like I am still blocked from adding Codecov back the MolSSI organizational account saying that it is already installed. Looking through the MolSSI organizational account none of the repositories or the organizational level have the App mentioned anywhere. Should I give this additional time or contact GitHub?
I don’t think I have a way to search apps by customer so if it’s showing removed, but says it’s not I would reach out to GitHub support.
Thanks! Sent GitHub support an email about this.
@drazisil Ok got a response back, apparently just uninstalling the app isn’t sufficient as we need to kill off billing and a few other items.
Still having issues however, see this PR here where the CI passed an hour ago. Git commit: dfdbe9fe68c246e68bf02883e1e8d2a32f6ba455
@drazisil To make this even weirder, it appears that Codecov is not triggering for me, but works for others:
Me (no Codecov) - PR, SHA: c1b0c6ad0ff707bf554c5f2fad76b23803604fd1
Collaborator (Codecov works!) - PR, SHA: 15667faea7f13f71d78f77726313bbd2f25fa6a6
@dgasmith Here’s the error your commit threw
WARNING {"error": "HTTPError", "method": "POST", "ms": "101", "reason": "HTTP 400: Please upload with the Codecov repository upload token to resolve issue.", "status": 400, "url": "/upload/v4?commit=c1b0c6ad0ff707bf554c5f2fad76b23803604fd1&branch=master&job=575314828&pr=120&service=travis&build=588.1&slug=MolSSI%2FQCElemental&yaml=.codecov.yml&package=py2.0.15"}
This might be fixed by using the bash uploader, but its seems your upload was missing the upload token?
@drazisil It was my understanding that Codecov didn’t need upload tokens when using Travis or other authorized services and a public repo?
@dgasmith Good point.
Taking a look now to see what changed here.
Our apologies, we pushed a small change to how Travis tokenless uploads work and, despite this change passing all tests and working in our development servers, it appeared to cause problems for some of our users in production. Therefore, we’ve reverted the change until we can investigate more.
Can you please confirm this issue is resolved for you?
Retrigger Travis show it works:
Woohoo!
1 Like
I am facing the same issue with my PR. PR is getting updated with status checks but not the reports uploaded to codecov by that pull request commit. How do I check the connectivity to codecov from my git account?
Hi @satchava
If you add -v to your bash uploader command you will get verbose output and be able to determine if you are getting an error code from us, or a true network timeout.
This issue is happening again in the same repo for me.