CodeChecker store command silently corrupts data when storing with --trim-path-prefix

CodeChecker version: 6.15-54-gcd94f9e3

I was wondering why there were no reports listed under a specific run, after CodeChecker store command reported success:

CodeChecker store /home/codechecker/codechecker_results/qtbase-dev-20201029-ec407916 \
    --trim-path-prefix /home/codechecker/qt/qtbase -n qtbase-dev-20201029-ec407916 \
    --url http://localhost:8001/qtbase-dev

But the web UI at http://localhost:8001/qtbase-dev/reports listing the reports under the run was empty, same as the output of this command:

CodeChecker cmd results --url http://localhost:8001/qtbase-dev  'qtbase*'

Please note that the server is running as a different system user, using sqlite, and has no filesystem access to the client-side source files. The debug log of the server printed tons of errors, ending like that:

{report} [43784] <139735032895232> - plist_parser.py:148 parse_plist_file() - Parsing plist: /tmp/tmp4ugsrpo4/reports/qendian.cpp_clang-tidy_8244643767f4a1c2e46f498b98565fe5.plist
{server} [43784] <139735032895232> - report_server.py:2552 __store_reports() - Failed to get file path id for 'src/corelib/global/qglobal.h'!
{server} [43784] <139735032895232> - report_server.py:2527 __store_reports() - Parsing input file 'qrect.cpp_clang-tidy_8fd767b3e7df4319fb6a801a5375c456.plist'
{report} [43784] <139735032895232> - plist_parser.py:148 parse_plist_file() - Parsing plist: /tmp/tmp4ugsrpo4/reports/qrect.cpp_clang-tidy_8fd767b3e7df4319fb6a801a5375c456.plist
{server} [43784] <139735032895232> - report_server.py:2552 __store_reports() - Failed to get file path id for 'src/corelib/tools/qsharedpointer_impl.h'!
{system} [43784] <139735032895232> - store_handler.py:394 finishCheckerRun() - Finishing checker run
{server} [43784] <139735032895232> - report_server.py:2949 massStoreRun() - 'Anonymous' stored results (219885 KB) to run 'qtbase-dev-20201029-ec407916' in 17.62 seconds.

It seems the problem happend because of --trim-path-prefix. Re-running the store command without it, results in reports being properly stored to the database.

[gyorb]

Thanks for reporting the issue, I’m working on the fix.

[jimis]

Store command seems to work well now, and results are visible both on the web interface and on the command line. Thank you.