My CI is x86, ~10minute scan. My dev box is a M2 Macbook Pro, ~2hours.
Here’s a debug (-X log) of a local run in my TS project.
You can see some operations are exceedingly slow, and periodically, the scanner just kinda… hangs without clearly doing much of anything. I’ve annotated a few spots with inline comments (lines starting with ;).
Hi! Yes, we’re trying to use X64 GitHub Action Workers for CI because ARM64 is still unusable (tens times slower). Will be great to have the same performance. I think this is could be related to https://github.com/SonarSource/sonarqube-quality-gate-action project.
Let’s try to test Action on X64 and ARM64 instances.
If you don’t mind, can you share your CI/build definition or steps you are running with and your project (or similar project that you think is similar to yours)? I would like to replicate this issue as well.
No, there is definitely something strange about the runners. As for right now, sonarsource/sonar-scanner-cli, which is probably the Docker image you are using for your scanner, is not compatible with ARM64.
We have internal plans to support ARM64, but not just yet. Please try using X64/AMD64 and see if that helps.
I use native runners (GitHub instructions, not inside containers) on bare metal (ubuntu 22). All CI you can see in code above. Yes, I’m using X64 for bigger projects, hope it will be fixed in the near future, thank you)