Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[feat] Accept non-existing file paths in report-converter #4288

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[feat] Accept non-existing file paths in report-converter #4288

wants to merge 1 commit into from
+10 −13

Commits on Jul 8, 2024

  1. [feat] Accept non-existing file paths in report-converter 

    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
    bruntib committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    b23b256 View commit details
    Browse the repository at this point in the history