Hello, I want to know if merging ps_comments.db is possible in case PS Code Prover analysis for metrics was run in parallel by two persons on the same project but for different modules/sources.
Thank you,
Cristian
Best Answer
Hi Cristian,
instead of merging two databases, I suggest you to use the built-in import function.
To use it, open the results of one verification, choose the menu Tools/Import Comments... and from the dialog window, load the results of the second verification.
See thislink for more information on this feature.
Merging these files is not supported, however, you can use Polyspace Metrics to set up a results repository, which many different developers can use to submit comments to the same results.
Polyspace Metrics allows Developer A and Developer B to each download a copy of the results from Metrics, review and make comments, and then submit their reviews back to Metrics. As long as these developers did not edit precisely the same comments, all of the comments will be kept. If both developers provide comments for the same review points in the code, only the latest submitted comments will be kept for that field.
When dealing with orange checks, a good rule of thumb is to find the source of these checks so you can "work on it".
The GUI actually gives you this information first in the dashboard (see the graph 'Top 5 orange sources') and in the dedicated window named 'Orange Sources'.
Tip: when reviewing an orange check, in the 'Check details' or 'Result details' window, the "orange question mark" icon, when it is enabled, will open this 'Orange Sources' window and highlight the source for this orange check.
If you launch Polyspace in command line, the 'orange source' information is also available in the log file (look for 'Classification of orange check sources').
Once you know the source(s), the DRS and the stubbing are the main ways to reduce the number of orange checks.
For more information on how to deal with orange checks, please refer to the documentation, for examplehere.
Best Answer