Last analysis failed Analysis ID "AZXqqHP2IlL5bR2X1xIZ"

SonarQube Cloud
1

I’m seeing a lot of failed analysis on our CI, they usually end up working after main is merged back into the PR branch but it’s still pretty annoying

3

Other similar failure IDs:
AZXRp2AV5Qqsv1VF_EL1
AZXrNMCN6fAnHseYc-bk

4

Another failure ID, this time for an unrelated PR:
AZXwQnNTYKtrlJyqiGUQ

5

Additional failures:
AZX58g0P2DBYEM-XNQiU
AZX6ElwB4HvNUFsnsdzl

6

Hi @nmussy

what we can see in the logs is that multiple analysis are triggered for the same commit ids, and the analysis is failing because there was already a analysis run for the same commit.

org.sonar.ce.task.projectanalysis.step.ValidateProjectStep$ProjectValidationException: Report for commit ‘67a363f8b538be6d5b33841f97cbfd20fc2e27e6’ can’t be processed: a newer report has already been processed, and processing older reports is not supported. The last processed report was for commit ‘67a363f8b538be6d5b33841f97cbfd20fc2e27e6’.

We will continue the investigation. I can see that both of the runs are coming from autoscan, so multiple analysis is triggered for the same event.

Merging solves the problem as the merge creates a new commit.

Thanks
Csaba

8

Do you maybe have monorepo setup?

9

Hey Csaba_Feher, thanks for the reply.

Our project is indeed a monorepo, but as far as I can tell we have a single CI loop and we’re not triggering multiple SonarQubeCloud checks per commit

We are using Graphite, which quite often rebases and force pushes a given PR, but I don’t see how that would create duplicate git commit hashes (if that’s what you mean by commit IDs)

Let me know if you need anything else!

10

Hey @nmussy

To clarify the impact, could you please confirm that your quality gate is up to date with the value of the latest commit?
(I mean that you have the right results for the analysis, but you also get notifications of the failed results.)

We do not support Merge queues and have no direct support for Graphite; we suspect that Graphite does something under the hood in your setup that creates multiple commits for the same branch within a really low timeframe. For example, if Graphite does a quick rebase, push, and commit, push under the hood, we could face this issue.

This is only a theory so far, but it would help us if you have a public repo integrated with graphite to share with us or if you could create a reproducer for us.

Thanks
Csaba