**Last analysis failed** Analysis ID "cea97503-e4b5-459a-ad39-0ce9b73bd774"

SonarQube Cloud
1

Last analysis failed Analysis ID “cea97503-e4b5-459a-ad39-0ce9b73bd774”

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “cea97503-e4b5-459a-ad39-0ce9b73bd774”.

6

Hi @gte1

Here is the error:

ERROR: File source/firmware_version_app.h can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files

Could you double-check your project configuration? Here is some documentation about how to configure the Analysis scope.

7

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “AZBJ8GBeDqRwxbksZ64Y”.

8

We have not defined sonar.tests in the config file as we don’t have any yet
But we have another firmware_version_app.h in another directory ABOVE source
Could that be the cause?

Our config has source set to this: sonar.sources = source/

Also tried to exclude that file completely in
sonar.exclusions=source/application/Audio/**,source/TARGET_STM32F302xE/**,**/firmware_version_app.h

Still fails: Last analysis failed Analysis ID “AZBeCX3Y9bnwe3nJnwb_”

Then I added a sonar.tests=tests/ , where tests contains nothing except a dummy.txt file, but still fails Last analysis failed Analysis ID “AZBeL4H_iM8XDbYhG6S-”

10

Hi

The error is now:

ERROR: File source/framework/RTOSsupport/guard.h can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files

Could you please share a view of your project structure, so we have a chance to build a reproducer and understand why the paths collide?

11 
\
|
|-- other1dir
|-- other2dir
|-- other3dir
|-- other4dir
|-- other5dir
|-- other6dir
|-- other7dir
|-- other8dir
|-- other9dir
|
|--source
|    |--application (dir)
|    |     |--subdir1
|    |     |--subdir2
|    |     |--subdir3
|    |     |--subdir4
|    |     |--subdir5
|    |     |--other source files
|    | 
|    |--board (dir)
|    |     |--other source files
|    | 
|    |--framework (dir)
|    |     |
|    |     |--adstract(dir)
|    |     |--common(dir)
|    |     |--drivers(dir)
|    |     |--RTOSSupport(dir)
|    |     
|    |--TARGET_STM32F302xE (dir)
|    |     |--subdir
|    |     |--subdir
|    |
|    |-- other source files	
|--tests
|    |-dummy.txt
|
|-- misc other none-source files
|
|
12

Hi @gte1

For some reason, your project does not seem compatible with Automatic Analysis, and we can’t detect it properly.

Being conscious that it is far from ideal, I would suggest disabling Automatic Analysis and switching to CI-based analysis, triggering on your CI system.
If you have the same issue, a faster feedback loop would help you figure out the appropriate configuration or dig down to the root issue to report to us.
Would you not have the issue, it would be really helpful for us to know that so we can improve our Automatic Analysis.

Just as a note, we are conscious that the user feedback on Automatic Analysis is not great today, and we are actively working to improve it in the near future.

All my apologies for the inconvenience,
Claire