Last analysis failed Analysis ID "1d66a55d-71aa-4af2-9b67-ae4f116b530f"

Last analysis failed Analysis ID “1d66a55d-71aa-4af2-9b67-ae4f116b530f”

Background: I have a private GitHub repository, and there I switched the mainstream development branch. Since I cannot change the “MAIN” branch in SonarCloud, I deleted the project in SonarCloud, and re-created it. Since then, I triggered the analysis several times, but it failed. With the same configuration, I had successfully triggered the analysis before I deleted it - the analysis just did not find the “MAIN” branch (and consequently reported 0% coverage on new code and such).

Hi,

Are you using automatic analysis, or is this a failure in processing the background task (i.e. once CI-side analysis is complete and the report has been submitted to SonarQube Cloud)?

And can you provide the approximate date/timestamp of this error? That will help us find it in our logs.

 
Thx,
Ann

Ann, thank you for picking this up! GitHub states that the latest CI build (which included the SonarCloud step) failed at July 16, 2:18 PM GMT+2.

1 Like

Hi,

Thanks for the timestamp. And given that it’s coming from GitHub, I’ll assume that the failure is on the background task processing side.

I’ve flagged this for the folks with log access.

 
Thx,
Ann

1 Like

The analysis method was set to “automatic” by default. Turning this off resolved the issue.