Massive slowdown of scans using GitHub Actions

We have noticed a massive slowdown in the scans for our code base using GitHub Actions. The project is mostly JavaScript and has ~6k files and ~190k lines of code. Typically the scan would take about 30 minutes, but it’s now timing out after 6 hours (the max for a GitHub Action).
We’ve seen this with both sonarsource/sonarcloud-github-action@cb201f3b2d7a38231a8c042dfea4539c8bea180b and sonarsource/sonarcloud-github-action@5875562561d22a34be0c657405578705a169af6c. We are using GitHub’s ubuntu-22.04 runner.
What can we do to get the process time back down to normal?


Hi @dancook-sl,

Please see THIS announcement thread regarding the issue.


1 Like

Thanks for sharing that link. This looks like an issue I would have expected to see on the SonarCloud Status page In the future, how can I know when an ongoing incident impacts my use of the service?

Also, I am still seeing a slowdown in the scanning process. Is there any further word on resolving these issues?

Hi @dancook-sl

Could you activate the debug mode (by adding an argument to the action -Dsonar.verbose=true), and post here the full execution log with timestamps, for us to investigate where the slowness comes from?

Thanks in advance,

This eventually resolved itself, and the runs are back to more normal times of <10 minutes.

I’m glad to hear that, and I hope it will stay like this!

Have a nice day,

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