Last analysis failed: 5d5b1aa7-d5ff-4698-b84d-bdc2e13c423a

SonarQube Cloud
1

Just getting this error message.

Not sure what I should look at :wink:

Merci !

2

Hey @dadoonet, I had a look at the logs and it seems like your analysis failed due to the incident that we were experiencing yesterday during the same timeframe your analysis ran. Could you confirm if the issue still persists now that the incident is resolved?

3

Right. Now I have

There are problems with file encoding in the source code. Please check the scanner logs for more details.

I just don’t know where I can see the logs. Do you know?

4

You can’t see the logs yourself because you’re using automatic analysis, meaning, the analysis runs on our infra instead of on your CI (where you would normally be able to see the logs). The “Please check the scanner logs for more details” is misleading, we shouldn’t show you this, I’ll raise this with the developers to see if we can improve the wording.

That being said, I had a look at the logs and I found the encoding issues: you have some files under test-documents/src/main/resources/documents/ and integration-tests/src/test/resources-binary/samples/ with .pdf, .docx, .png
 extensions, which of course are not UTF-8. You could consider adding an exclusion to your .sonarcloud.properties, something like:

sonar.exclusions=**/test-documents/src/main/resources/documents/**,**/integration-tests/src/test/resources-binary/**
6

Fantastic. Thanks!

8

Does Sonarcloud read the sonar-project.properties file from the project?

Do I have to provide both .sonarcloud.properties and sonar-project.properties?

I tried with one or the other with:

And I’m still seeing the warning. Is there a way to see logs or reproduce locally to see exactly which files are seen as problematic?

9

When using automatic analysis, only .sonarcloud.properties is used, not sonar-project.properties.

If you want to reproduce locally, you will have to run the scanner yourself (which is basically what you would do in the CI if you were using CI-based analysis). I recommend you have a look at these docs.

If you let me know the analysis ID of your latest analysis, I can check the warnings again.