Troubleshooting
Analysis Errors
Unknown error (U10)
These errors indicate an unknown problem with our system. Our developers monitor closely for these types of errors. In most cases when they occur, we are already looking into it.
If you see this error, please contact our support team with your project name and a screenshot.
Inconclusive commit status (U11)
This error occurs when pull request analysis starts, but Qlty hasn’t posted a conclusive (green or red) status back to GitHub within 15 minutes. At that point, Qlty will mark your GitHub commit status as error
(red).
It’s possible that the analysis succeeded, but an external factor interfered with posting the status back to GitHub (e.g. a GitHub outage, network issue, etc.). If this happens, you will need to retry the analysis.
Analysis timeout
We apply timeouts to analysis runs to keep things running smoothly.
If you find that a pull request or commit analysis frequently times out, we recommend trying the following steps to speed up the process.
Ignore files or directories
When analysis times out, start by identifying directories and files you can ignore from your analysis. You can specify these exclusions in your qlty.toml
configuration file.
Ignoring directories and files reduces the time Qlty spends analyzing your project. You can ignore files and directories for all plugins or specific plugins.
In general, we recommend ignoring:
- Vendored code
- Generated code
- Production assets such as minimized files
- Automated test suites
In order to receive the benefit to analysis speed from ignoring files, ignore them in qlty.toml
(not the web application).
Disabling plugins
Certain static analysis tools are slower than others. Disabling slow static analysis tools can speed up your analysis times.
Missing analysis results
Problem: No code review comments or commit statuses are showing on my pull requests.
If you’re not seeing pull request statuses or summary/code comments for your project, first confirm that these features have been enabled under Project Settings -> GitHub Integration
. If these features are enabled, please contact support.
Code Coverage Issues
Coverage uploader error
Problem: The coverage uploader is failing with an error.
Please capture the error message you’re seeing, along with your workspace and project names, and contact support for further assistance.
Missing code coverage results
Problem: I am not seeing code coverage data when I would expect to.
Please ensure the following:
- You are providing the correct coverage token to the coverage uploader.
- The
file
argument is pointing to a valid path to the coverage report (e.g.,some/path/lcov.info
). - If applicable, you are correctly specifying the
add-prefix
argument.
If you have confirmed that these values are correct and still missing code coverage results, please contact support for further assistance.
Inaccurate code coverage results
Problem: My code coverage shows X% but it should be Y%.
To address discrepancies in code coverage reports, ensure the following:
- Instrumentation: Verify that your test suite is correctly instrumented to measure coverage.
- Coverage file path: Make sure the path to the coverage file is accurate and the file itself contains valid data.
Unexpected total coverage change
Question: Why did my total coverage go down?
Unexpected changes in total coverage can happen due to several reasons:
- Deleting code: If you remove code which has coverage, your total coverage percentage will decrease.
- New, uncovered Code: Adding new code that is not covered by tests can reduce your overall coverage percentage.
- Changes in Existing Tests: Modifying or removing tests can impact the coverage if those tests previously covered parts of the code that are no longer tested.
Other Troubleshooting
Missing project
Problem: When I go to add a repository as a project, it’s not visible in the list.
If you’re trying to add a project but it doesn’t appear in the list of available projects, first confirm the following:
- Our GitHub Application installation must grant access for that repository.
- The repository must be accessible by you on GitHub.
- Double check that someone hasn’t already added the repository to Qlty
Permission denied error
Problem: I am trying to access a workspace or project but am getting blocked.
If you encounter a permission denied error, consider the following possible causes and solutions:
-
Insufficient access to the GitHub repository: Project-level permissions on Qlty are determined by a user’s GitHub permissions. To view project analysis on Qlty, you need read access to the repository on GitHub. To view project settings on Qlty, you need admin access to the repository on GitHub.
-
Multiple Qlty users: Having more than one Qlty user can cause confusion. If this is the issue, you are likely logged into a user account that hasn’t been added to the workspace owning the project you are trying to access.
Missing link to Settings
Problem: I believe I have workspace admin access but I don’t see a link to settings.
To manage workspace settings on Qlty, you must be an admin on the associated GitHub account. Please ensure that you have the appropriate permissions before attempting to access these settings.
Private linter plugins or configurations
Problem: My build is failing because a linter can’t find my private gem/package.
Qlty is unable to access any private gems, packages, or registries during analysis. For example:
-
Rubocop:
Unable to find gem our-private-rubocop-config; is the gem installed?
- Some users may maintain their Rubocop configuration within a private gem; this is not currently supported.
-
OSV-Scanner:
failed extracting pom.xml
- OSV-scanner scans for vulnerable dependencies, and it cannot access private packages or package registries. It is possible to configure OSV-scanner to ignore specific packages, as documented here.