The last analysis has failed: Analysis ID "7c56d75d-4748-4172-bbc1-2280153ff21b"

SonarQube Cloud
1

I’m working on setting up a project and analysis is failing.

Analysis ID “7c56d75d-4748-4172-bbc1-2280153ff21b”

I’d like to resolve this myself, but have nothing to go on.

I tried running the scanner locally:

docker run \
    --rm \
    -e SONAR_HOST_URL="https://sonarcloud.io/" \
    -e SONAR_SCANNER_OPTS="-Dsonar.projectKey=key-path-removed-by-me-here" \
    -e SONAR_TOKEN=""
    -e SONAR_LOGIN="login-path-removed-by-me-here" \
    -v "path-removed-by-me-here:/usr/src" \
    sonarsource/sonar-scanner-cli

That runs fine, runs across ~1600 files, and doesn’t have any failures on scanning.

I would like help for how to resolve the issue myself, but if that can’t be done, please DM me with what the error is.

2

Hi,

Can you provide the approximate date/time of the error? It will help us find it in our logs.

 
Thx,
Ann

3

Thanks for helping @ganncamp , the change I am working with was pushed at 8:53am EDT, so I think the error would have been shortly after that.

1 Like
4

Hi,

Thanks for that! I’ll flag this for the folks with log access.

 
Ann

6

I’m still trying here. New error id:
Last analysis failed Analysis ID “AZW0AUYb6ZL14W3Aml5q”

That was at about 10:43am EDT March 20, 2025.

I still need help with this and now cannot use our paid account to scan this codebase.

1 Like
8

Hi @craig-landry

We can see the scanner failing with this error:

Caused by: java.lang.IllegalArgumentException: Line 3052 is out of range for file src/app/main/apps/flowBuilder/mock/chatbot.js. File has 3051 lines.

Since the analysis succeeds on your local environment, we suspect encoding configurations differences between your environment and the automatic analysis environment.

We could also see other files analysis succeeding (the failing file is the 514th one to be analyzed). For example this one could be processed: src/app/main/apps/global-analytics/components/AnalyticsChatLogs.jsx

We suggest you check the encoding and contents of the failing file and see if these can be changed.

Hope this helps,
Alex

10

Following up on this endeavor: It turned out that there were some odd newline characters. Replacing them with the usual \n got that file fixed up and we’re good to go here now.

2 Likes