Failing analysis ID: e118be3f-4078-4c61-ab14-438f05869ccf

SonarQube Cloud
,
1

Automatic scans of our GitHub C++ repo are failing with this code this morning. Everything was working properly until now. What do we do now?

4

Hi,

This looks like a problem on our side. I’ve flagged it for the team.

 
Ann

5

Thanks, next update gave error id 3ac2de6d-3f37-4c7a-94aa-3d7fd434decb

6

Hey, we appear to have the same issue - eb94e859-53ec-4c56-943e-5360468faa4a

7

Any progress on this or how to get around the problem?

8

Hi, we experience same issue.
492a2108-cfc7-402f-aa77-814cdaed887d
Do you have any updates?

9

Wer are also having issues and would be interested in an ETA or a short description of the underlying issue

10

Analysis status

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: c907ae9f-f718-43b8-b286-c486ade2d40e.

11

Another one.

Analysis status

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: 5246cc9a-86ec-4e47-91ad-905951fe531c.

12

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: ba8980e0-4590-4295-9052-3f5cb2c7b76a.

13

Hi all! We are experiencing an incident with automatic analysis for C/C++, which is most likely the reason why you are having these errors. You can follow the status of this incident in our status page: https://status.sonarqube.com/

If anyone here believes their issue to not be related to this incident (for example, your project has nothing to do with C/C++) please let me know.

14

My project was iOS/Switft.

15

Our project is Java based, just triggered another analysis and will report the results here.

Still failing, turned on debug log now.

We get a 404 when calling
15:17:31.811 DEBUG → POST https://api.sonarcloud.io/analysis/analyses (181-byte body)

15:17:32.123 DEBUG ← 404 https://api.sonarcloud.io/analysis/analyses (311ms, 0-byte body)

I think this is a different issue then the ones reported here :frowning:

16

Just fyi, it was an expired sonar token on our end.
Sorry for the noise.

17

our issue was related to line of code, after we bumped that, builds started again

18

The incident has been resolved, apologies for the inconvenience! If the issue persists, it might be a different problem (@80bower perhaps this is your case), please let me know.

19

What was the issue?

20

@80bower there was a problem with the latest deployed analyzer for C/C++/Objective-c. It has been rolled back. From what I have seen, your analyses were being sent to that analyzer, most likely because there is some C file in your Swift project, so it seems to me you were affected by the same incident. Is your analysis working again?

21

Thanks to @BillHoover, @kristiankunc , @jangalda-nsc and @80bower for reporting the issue and for your patience!
@spongenee and @bahag-klickst: thanks anyways for reporting, even though in the end your issue was different. In the case of @spongenee, it was me who merged the original thread into this one, my bad!