Open gyorb opened 6 years ago
It was implemented in #639 and it works the same now: https://github.com/Ericsson/codechecker/blob/12fedce8f506ebc992df177d8755bc54689c9a08/analyzer/codechecker_analyzer/cmd/parse.py#L672-L678
I do not now what was the reason behind this but I removed it in #2616.
Could that be the original reason if there is some relative file path in the report it can not be parsed? Usually the file path in the reports are relative if the include paths or the file path is relative in the compile command database. If there are only absolute paths everything should be absolute in the generated reports.
the parse command changes directory to
working_directory
from metadata.json before parsing the plist files why is this needed?If a compressed report directory is sent to another user the parse will not work.