Description
JUnit coverage report successfully uploads from CircleCI using codecov orb v1.0.5, but report cannot be found in codecov app.
Repository
https://github.com/hboylan/recipes-api
Versions
Latest Chrome
CircleCI v2.1
I think you may be hitting the same issue that we’re discussing again here: Codecov status stuck at "waiting for status to be reported" - #12 by elucidsoft
For us, there seemed to be some strange issue with missing coverage for the base for a PR. But we re-ran our test on circie-ci for the base (we use the python uploader, which reports success), and still nothing.
Okay. I saw that thread as well, but haven’t seen “waiting for status to be reported”. If I go to the “Commits” section for my repo, I do see “Processing…” for all commits.
This seems pretty ridiculous to me. Report was successfully uploaded with codecov’s own tool, but hasn’t processed successfully at all for my repo. Looking at Coveralls as an alternative…
Just to be complete, the “waiting for status…” is from the GitHub integration:
But I get the same behavior as you describe on the Codecov website. I don’t think we can directly verify the S3 upload (the URL isn’t given), so the closest we can get is the page you started with describing, the “unable to find report…” page.
I’m guessing all the folks with problems are using codecov for free, open source projects? Codecov is clear that they support such projects on a “best effort” basis - but I guess they have less bandwidth for this recently.
I see, thanks for clarifying. The codecov integration is also enabled for my GH repo as you mentioned, but I didn’t see the checks in any of my PRs. Just uploaded report directly from CircleCI pipeline using the Codecov orb linked in OP.
Thank you for the reports, everyone. We are investigating this, since it doesn’t happen for everyone it’s being hard to track down. We are seeing that, for those of you it is affecting, that it’s happening very often, so I completely understand your frustration.
Couple of questions:
- Did this ever work correctly for you, and if so, do you know roughly when it started happening?
- Can you think of any changes you made around this time?
@drazisil This is my first time trying to use codecov on a personal project. I’ve seen it work great on other projects, but it hasn’t worked at all since I’ve tried integrating myself as described.
Some (hopefully) helpful debug info:
- Codecov was added on a feature branch, not master
- Codecov was added on a later commit, not the first one (4th commit on this PR)
- My codecov report is generated with jest-junit
- My codecov report is uploaded with codecov-circleci-orb successfully as reported in OP
Thanks, @hboylan
Those points shouldn’t matter, but thanks for bringing them up. Can you share a commit SHA you are getting this error on so I can check the logs and confirm this is the issue we are investigating?
EDIT: Actually, you said you installed Codecov to a non-master branch? That might matter. Can you explain how you did this, and would it be possible to move it to master to test if that changes anything?
First successful successful upload was commit fbe5c6b27311a1be9b94b058afcb141c8ff1464e
Related CircleCI job is here
Appreciate you taking the time to look into this @drazisil!
Ah, you mean that your first commit to Codecov was on a non-master branch?
Can confirm this commit is an instance of what we are investigating currently for this thread.
I don’t have more I can report other then it’s being actively investigated and I’ll update when I have one.
Correct.
I actually traced the original codecov report upload farther back to 0c87af16aa3b415042cffafa676c3c7e9413935b on branch “circleci”.
It was this job from before I renamed it “test”
FWIW, I am in a very similar situation, evaluating codecov, first commit was on a non-master branch using CircleCI Orb, Example commit SHA: b7260d322f50f56b761f6d97a6c691205dd546f0
Very interesting.
Two more questions then (at an attempt to pattern match)
1: Did everyone start uploading to a non-default branch?
2: Is everyone using the orb?
2.5: Does this happen if you use the bash uploader?
Yes to all for me. Just tried the bash uploader and the report still cannot be found in codecov.
Drat. Thank you for trying.
Just got codecov to recognize my report for the very first time.
- Checkout master branch on local machine
- Generate jest coverage report
- Push commit to master branch
- Upload coverage report with bash uploader
- Report shows up in codecov
1 Like
Sadly this didn’t work for me…default branch in our repo is development, just pushed to it and uploaded a coverage report, but I receive the same message. In the default view where it lists “All recent commits” it says “Unable to find commit in Github”, SHA: 00a7a6c15c2ce37713e193b68ebe2c8008daad12
Edit: Also worth noting that if I go to Codecov that all are listed as “Processing…”
This definitely sounds like the issue in this thread. We are actively investigating and I hope to have an update soon.
2 Likes
Hey all, thanks for your contributions and apologies for the issue.
We started an open issue tracker on this here: CLOSED ISSUE INVESTIGATION: Report stuck in processing + Unable to find report content in storage archive
This is affecting about 1% of users. We are rapidly looking for a root cause fix or a workaround we can deliver to you all. More updates to come on the thread above.
1 Like