Last analysis failed Analysis ID "AZKL0wc-hIKQEmIltf88"

SonarQube Cloud
1

Hello!

I am seeing the error in the topic together with an encouragement to post it here.

I imagine that it fails because of some configuration in “.sonarcloud.properties”, but perhaps I am mistaken.

If so, why not expose that information to the user?

Thank you and have a great day!

2

Hi,

Could you share the approximate date/time this happened to help us narrow down our log search?

Also, can you share your .sonarcloud.properties configuration, redacted as necessary?

 
Thx,
Ann

4

Hi Ann

This happened around 2 hours ago in two consecutive runs of the same PR.

sonar.projectKey=Z-Wave-Alliance_z-wave-stack
sonar.organization=z-wave-alliance
sonar.sources=.
sonar.exclusions=<removed>
sonar.tests=.
sonar.test.inclusions=**/tests/**,**/Test/**,**/test/**
sonar.cfamily.build-wrapper-output=build_wrapper_output_directory
sonar.coverageReportPaths=coverage.xml
sonar.coverage.exclusions=<removed>

Hopefully this can shed some light on the issue.

Thank you!

5

Hi,

I don’t have log access, but while we wait for the arrival of those that do…

It’s likely to have something to do with this:

At a guess, you’ve got an overlap in the two sets (sources and tests) described by these four properties.

Is it feasible to narrow the sonar.sources and sonar.tests definitions? Something like:

sonar.sources=specific/directories,in/a/comma,delimited/list
sonar.tests=a/tests,b/tests,c/Test,d/test

 
Ann

6

It would surprise me if those configuration options are the root cause because we have used exactly the same configuration file (although with another filename) for manual scanning prior to enabling “Automatic Analysis”.

Edit: but I will give it a shot if you don’t get any other clues from the logs.

Edit 2: I enabled Automatic Analysis around the same time as the PR failed to be analyzed. It’s the first analysis done automatically.

7

Hi,

Like I said, I don’t have log access. Those that do are (mainly) in Europe, and so are done for the day already.

But they’ll be along eventually.

 
Ann

8

No worries. I am located in Europe too, so I will check back in tomorrow.

Thank you!

9

Turns out the failure was caused by one or both of the two following lines in the config:

sonar.cfamily.build-wrapper-output=build_wrapper_output_directory
sonar.coverageReportPaths=coverage.xml

I removed both at the same time, but since both are related to running SonarCloud “manually” from CI, they should not be present when running Automatic Analysis.

1 Like
11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.