Your analysis with "analysis id" has failed

Your analysis with ID “$analysis ID” has failed: An error has occurred with your code repository platform (GitHub, Bitbucket, Azure DevOps, or GitLab). Please try again.

Did it really say $analysis ID” or did you redact the ID? You’ll ned to post it here if you want help. :slight_smile:

I have redact it ,let me share the complete message and its frequently happening across multiple repositories which are connected with github

Last analysis failed Analysis ID “AZEmep2ZG0cZydZ_FCip”

Your analysis with ID “AZEmep2ZG0cZydZ_FCip” has failed: An error has occurred with your code repository platform (GitHub, Bitbucket, Azure DevOps, or GitLab). Please try again.

Note: We are facing a lot of inconvenience and we need to do a lot overrides in merge bcoz this analysis are not getting completed very frequently, we have sufficient LOC license is available in the org.

Hi @shivagangadhara ,
Does the git clone with --recurse-submodules works on this project ?

the integration is via github apps b/w sonarcloud and github and these issues mainly on PR mergers.

Yes, the git clone with --recursive-submodules works on the project.

let me know if you need any further details on this

Do you have access to project backgroud tasks (in project setting) ? You will find failed tasks with maybe some information.

There is no failed tasks available in the background task in the project and only success tasks are visible

Please let me know , if anything else can be checked

1 Like

Hi,

Any update on this issues, we are still facing the same problems

Hello @shivagangadhara ,

Based on the Analysis ID, we found in the logs that the scanner failed to clone the Github repository, with this error message:

Fatal: couldn't find remote ref refs/pull/1474/merge

Does the ref exist at the time of the scan?

Yes, Its available

The best guess is that either the pull request was deleted or there were some permission issues communicating with GitHub when the automatic analysis was run.

Looking at the logs again, there seem to be newer pull requests that have successfully been analyzed (pull/1476) so I will assume this is no longer an issue.

We have merged a fix for this issue, let us know if you are still facing the problem.

You can find more details in this thread.