search

initc3 / HoneyBadgerMPC

Robust MPC-based confidentiality layer for blockchains
GNU General Public License v3.0
131 stars 64 forks source link

Codecov reports are not available -- Github checkpoint hangs #397

Closed sbellem closed 4 years ago

sbellem commented 4 years ago

Although the report upload appears to be working when looking at the log on Travis CI, the report is not available on Codecov, and the integrated checkpoint in Github hangs.

Codecov issued the following:

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.

An email was sent to Codecov and this issue will be used to keep track of the progress.

sbellem commented 4 years ago

UPDATE: Gabriel (@gambreu) from @codecov wrote:

Thanks for reaching out to Codecov!

We're looking forward to solving this as soon as possible. I've escalated your request to a Support Engineer who will circle back shortly.

sbellem commented 4 years ago

UPDATE: Gabriel (@gambreu) from @codecov wrote:

We've executed the workaround for you and the issue should be resolved.

Thank you for your patience.

But I am not sure it is resolved because despite what appears to be a successful report upload: https://travis-ci.org/initc3/HoneyBadgerMPC/jobs/613722988#L875, the report cannot be found on codecov.io: https://codecov.io/gh/initc3/HoneyBadgerMPC/pull/399.

sbellem commented 4 years ago

Will close as the issue is now fixed. From @gambreu of @codecov:

Hi Sylvain!

I'm writing to inform we have found the 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 the Unable to find report content in storage archive error message, but that would only be in cases where the error existed prior to the current bug in question. Reasons for this 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).

We will begin removing users from the workaround approach we had followed and adding them back to our main processing worker.

Thank you!