improved errorhandling of analyzer information loading

[firewave]

No description provided.

[firewave]

The files.txt errorhandling cannot be tested because because the files is being rewritten on each start-up. The listed XMLs are also read beforehand so any issues introduced to them are caught in earlier code.

This is to catch issues with generating this data during run-time. This is done since we do not (can) use the XML library to write it. I need to modify that data after it has already been written to inject the unmatchedSuppression warnings (at least in my current approach) to fix the remaining issues with them when using a builddir.

[firewave]

This exposes an issue with --clang and --cppcheck-build-dir:

FAILED test/cli/clang-import_test.py::test_cmd_std_c_builddir - assert "nofile:0:0: error: '/tmp/pytest-of-runner/pytest-0/popen-gw0/test_cmd_std_c_builddir0/b1/test.a1' from '/tmp/pytest-of-runner/pytest-0/popen-gw0/test_cmd_std_c_builddir0/b1/files.txt' not found [internalError]\n\n" == ''
  
  + nofile:0:0: error: '/tmp/pytest-of-runner/pytest-0/popen-gw0/test_cmd_std_c_builddir0/b1/test.a1' from '/tmp/pytest-of-runner/pytest-0/popen-gw0/test_cmd_std_c_builddir0/b1/files.txt' not found [internalError]
  +

I filed https://trac.cppcheck.net/ticket/14456 about this.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud