Could not read report from S3 for task AXM0Vsyz9Kn4c5Jad2QU

SonarCloud
1

Any ideas why its failing? Failed today July 9, 2020 12:09PM

5 Likes
2

I’m having the same issue and also want to know :slight_smile:

1 Like
3

+1 on same issue.

4

+1 on same issue.

5

I also posted in the “report a bug” section: Could not read report from S3 for task [hash] when running publish quality gate in Azure DevOps

6

+1

same issue for us starting today too

7

Same here

8

Same issue for us. Looks like it started around 11:42am EST.

9

Same issue .

10

Same issue, fix this please :frowning:

11

Same issue using SonarScanner for MSBuild

12

+1. Thanks for looking into it Sonar team!

13

Same issue

14

I’m not sure it’s helpful, but I sent a tweet to the Sonar Cloud status account. Looks like they have an update now saying there is a problem and they’re investigating: https://twitter.com/sonarcld_status

2 Likes
15

Their status page now shows “Major Outage” for “Analysis Computation”

1 Like
16

Hi All,

A bug in our last deployment has lead to a problem processing scanner reports. Since then we have mitigated the issue and the service is back to operational, while a real fix is in progress.

You can track the progress on the fix and the status of the service on our status page: https://sonarcloud.statuspage.io/

Thank You for signaling the issue (we did detect on our side, but vigilance is always good).

Janos @ SonarCloud Team

17

@janos will my PRs get unblocked at some point? Or I have to trigger analysis one more time?

18

You have to trigger them one more time. (You can already do it now.)

19

Unfortunately, there is no such option on GitHub. So I have to commit some fake commit to trigger analysis.

20

Can I make a feature request - have a button on GitHub to re-run failed or timed out analysis?