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:
- If the repo never had a report in first place to locate
- 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.
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.
Jerrod and the Codecov Team