CLOSED ISSUE INVESTIGATION: Report stuck in processing + Unable to find report content in storage archive

UPDATE DECEMBER 2ND 2019:

We have found root cause of central issue regarding Unable to find report content in storage archive errors.

In summary: a refactored worker we delivered to Codecov.io application was in some cases picking the wrong file processor. That bug has now been squashed.

There are users that may still see this error: Unable to find report content in storage archive, but that would only be in cases where the error existed prior to the current bug in question. Reasons are likely:

  1. If the repo never had a report in first place to locate
  2. If reports are intermittently stuck in “Processing” state, potentially due to number of uploads or size of uploads (or both).

If we had added you to our workaround approach, we will begin removing users from that workaround and adding them back to our main processing worker.

Thank you!


Original Post: November 5th 2019

Hello Codecov Community,

Over the last two weeks, we’ve been noticing an issue substantially impacting about 1% of organizations.

Users experiencing this error will see general issues like Report stuck in processing and the specific issue Unable to find report content in storage archive.

We are doing in-depth investigation to fix the root cause issue, and simultaneously looking for workarounds for affected users.

If we find a workaround before a root cause fix, we will manually help users utilize the workaround and update here accordingly.

Thank you everyone for your patience, and apologies for the issue.

Best,
Jerrod and the Codecov Team

7 Likes

Hello everyone,

Thanks for your patience while we investigated this issue. We’ve been able to identify and push a manual workaround approach for affected users, simply message us:

Your relevant code host (Github/Gitlab/Bitbucket) organization name to hello@codecov.io and mention you are experiencing Unable to find report content in storage archive. We will provide change to your account.

Meanwhile, we are still investigating a longer term fix and will update thread again once found and deployed.

Jerrod

I changed one of my GitHub repo’s name. And Codecov bash script keeps sending reports to the old Codecov repo. Is my problem related to this issue here?

Hey @bofeizhu – very unlikely to be the same issue. I saw you filed a separate post on this, thanks!

Thanks for looking into this, which also affects our GitHub project.
The default branch is dev, and I wonder if this current issue is related to the project badge showing “unknown” or is it a different issue?