CodeChecker parse command should provide analysis status per source file #4271
Description
In the VSCode plugin, in the “Reports in current file” view it is not possible to know if the analysis of a file was correct, failed and whether it is up to date. When there are 0 findings for a source file, we don’t know whether there were really 0 findings, or the vscode plugin is not showing any reports because the analysis was faulty. See Ericsson/CodecheckerVSCodePlugin#149
It should be possible (using the CodeChecker parse command) to query the analysis status of a source file. e.g.:
CodeChecker parse –file source.c –analysis-status
Expected output:
clangsa : successful analysis
clang-tidy: successful analysis
cppcheck: failed analysis
fbinfer: outdated analysis
In case analysis was never run.
No analysis result found for source.c
Then the VSCode plugin would be able to visualize the analysis status.
In the current CodeChecker version there is one plist file per analysis invocation. The name of the file contains the name of the source file, the hash of the compilation action and the analyzer name (source_file_analyzer_compilation_hash.plist).
An improvement possibility is that CodeChecker stores the following additional info in the PLIST file
Analyzer name
Analysis result: successful, failed
Source file content hash (to be able to indicate if the result is outdated)
Analysis execution time