Repository navigation
Improve error handling for unbuilt CodeChecker launcher - #5182
Merged
bruntib merged 1 commit intoNov 12, 2026
Merged
Conversation
Detect missing packaged CLI files and add launcher regression tests.
bruntib
approved these changes
Nov 12, 2026
Contributor
|
Thanks for the improvement! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improve the error message displayed when bin/CodeChecker is executed directly from an unbuilt source checkout.
Previously, the launcher failed with a Python missing-file error because the packaged CLI entry point was unavailable.
The launcher now detects the missing entry point and displays an actionable error message explaining how to build and run CodeChecker.
Changes
Check whether the packaged CLI entry point exists before launching Python.
Display a helpful error message and exit with a nonzero status when the package has not been built.
Preserve the existing behavior for valid package layouts.
Add four regression tests covering launcher behavior and error handling.
Testing
4 launcher regression tests passed.
Pycodestyle, Pylint, syntax checks, and whitespace checks passed.
Verified compatibility with the existing built package.
Broader analyzer suite: 127 passed, 7 failed, 11 errors, 10 skipped. Remaining failures and errors were associated with unavailable Clang/clang-tidy tools.
Full package builds, web tests, and functional tests were not run.
Closes #3371