-
Notifications
You must be signed in to change notification settings - Fork 382
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.
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
--trim-path-prefix broken in 6.24.0 #4354
Comments
We suspect that this also impacts |
I encountered the same issue. codechecker/tools/report-converter/codechecker_report_converter/report/output/html/html.py Line 240 in 3229b9b
Changing Apparently, Version Info
I directly edited the contents installed by pip ( Edit: This might be more robust (i.e., not have unintended side-effects): diff --git a/tools/report-converter/codechecker_report_converter/report/output/html/html.py b/tools/report-converter/codechecker_report_converter/report/output/html/html.py
index c102199c..85bacfed 100644
--- a/tools/report-converter/codechecker_report_converter/report/output/html/html.py
+++ b/tools/report-converter/codechecker_report_converter/report/output/html/html.py
@@ -309,7 +309,7 @@ class HtmlBuilder:
table_reports = map(lambda data: {
'link': os.path.basename(data['link']),
- 'file-path': data['report']['fileId'],
+ 'file-path': self.files[data['report']['fileId']]['filePath'],
'report-hash': data['report']['reportHash'],
'checker-name': data['report']['checker']['name'],
'checker-url': data['report']['checker']['url'], |
Describe the bug
We just upgraded from CodeChecker
6.23.1
to6.24.0
and the--trim-path-prefix
option toCodeChecker parse
appears to have stopped working as the generated HTML pages are using the absolute path to the build folders on our Jenkins machines now.CodeChecker version
To Reproduce
After analyzing the code, run
CodeChecker parse --export html --print-steps --trim-path-prefix "<absolute-path-to-source-code>" --ignore <our-skipfile> --output "<build-dir>/code-checker-report" "<build-dir>/code-checker"
.Steps to reproduce the behaviour:
Expected behaviour
In the report generated by
6.23.1
it looks like this:In the report generated by
6.24.0
it looks like this:Desktop (please complete the following information)
The text was updated successfully, but these errors were encountered: