Hi,
Welcome to the community!
Only the latest version of SonarQube Community Build is considered active, so you’ll need to upgrade and see if the situation is still replicable before we can help you.
Your upgrade path is:
9.9.6 → 24.12 → 25.5
You may find these resources helpful:
- Upgrade Guide
- Upgrade notes for 9.9 to 10.7 (when SonarQube Community Edition switched to SonarQube Community Bulid)
- SonarQube Community Build Upgrade Notes (all upgrade notes since the switch)
If you have questions about upgrading, feel free to open a new thread for that here.
Regarding your question, this is likely a problem with a path mismatch in the coverage report between what SonarQube sees during analysis and the file paths in the coverage report. If you’re still seeing the problem after your upgrade, come back to us with your full analysis log.
The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.
This guide will help you find them.
Ann