Skip to content
Discussion options

You must be logged in to vote

Hello,
It depends on how the review status was set. If it's set on the GUI, then it belongs to the report hash and this information is stored in the database. For this reason, the review status set in the GUI persists.
If the review status is set by a source code comment, then it belongs to that report instance only, and will be set after the next storage either way.
If the review status is set by "CodeChecker cmd suppress", then it doesn't persist. However, this command requires a config file that should be used for each storage event in order to keep consistency. Also, we plan to deprecate this command, because it's easy to make inconsistency by using it.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by jimis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants