[feat] Accept non-existing file paths in report-converter #4288
Conversation
This file contains 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
Some analyzer tools (e.g. sanitizers) give an output that contains relative source file paths. When report-converter is executed from a directory where these absolute paths are not valid, then reports are simply not generated. If all reports contain such a relative path, then this message is given by report-converter: No 'lsan' results can be found in '...' This message is obviously false. This patch allows non-existing file paths in the analyzer outputs. Using further CodeChecker commands (store, parse, etc.) will emit an error message on these paths anyway, but at least we get rid of the incomprehensible error message above. Fixes Ericsson#4280
bruntib
added
CLI 💻
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.
Some analyzer tools (e.g. sanitizers) give an output that contains relative source file paths. When report-converter is executed from a directory where these absolute paths are not valid, then reports are simply not generated. If all reports contain such a relative path, then this message is given by report-converter:
No 'lsan' results can be found in '...'
This message is obviously false.
This patch allows non-existing file paths in the analyzer outputs. Using further CodeChecker commands (store, parse, etc.) will emit an error message on these paths anyway, but at least we get rid of the incomprehensible error message above.
Fixes #4280