Polyspace justifications added inside the code not available in generated polyspace reports

Hello,

I have observed that the polyspace justifications that are added inside the code as a code comment, are not available in the generated polyspace pdf reports.

In the polyspace access server these justifications can be correctly viewed (as shown in the below image). However, the status of the warnings is still "Unreviewed" in the generated polyspace pdf reports.

Could you please provide a solution to this issue?

Best Regards,

Narayan

Answer 1

[Andreas Apostolatos]

Hello everyone,

The cause of the issue was that the code annotation was added one line above the line of code that resulted in the defect and not on the same line of code, which is the expected workflow. See the following MATLAB Answers thread for more information,

https://www.mathworks.com/matlabcentral/answers/839120-why-isn-t-a-justification-appearing-in-the-generated-polyspace-report-although-i-can-view-it-in-the

Kind regards,

Andreas

Answer 2

[Anirban]

Did you generate the report from a result after uploading to Polyspace Access? This workflow seems to report all review information, whether entered through code annotations or through the Access UI.

To generate a report from a result uploaded to Polyspace Access, you have to use the polyspace-report-generator command with -host-name and -run-id. (Note also that prior to generating reports from Polyspace Access on an HTTPS, you have to configure a keystore using the -configure-keystore option.)

[Narayan Narvekar]

Hi,

Yes the reports are generated from a result after uploading to Polyspace Access. We fetch the latest RunID from Polyspace Access. We run polyspace-report-generator with this RunID as a parameter. Also, the keystore configuration is only for accessing Polyspace Access via HTTPS and I believe it does not have anything to do with these issue.

Also, the comments entered in the Polyspace Access UI are being exported to the reports. The issue is only with the code comments that have been added.

Best Regards,

Narayan

[Anirban]

Yes, the note about configuring keystore is for HTTPS servers only and is unrelated to the problem.

Is this issue happening for all projects or a particular one? I tried the workflow on my end and it seems to report the information from the code annotations.

You can also generate reports prior to uploading to Access using the polyspace-report-generator command directly on the results folder. Do you see the review information in that case? (I am asking this just to check if going through the Access route is somehow causing the review info to not show up.)

[Narayan Narvekar]

Hi,

We tried generating the reports directly from the results folder. Now, the code justifications are exported correctly into the pdf reports. But this solution does not work well, because the comments from the Polyspace Access are not covered in the report.

So there seems to be a problem in the Polyspace Access.

Best Regards,

Narayan

[Anirban]

Yes, this will not solve the problem. The workflow of uploading to Access and then reporting the results with justifications, is the intended one. I just wanted to see if there is something specific in the nature of the code annotations that was causing them to not be reported.

If the issue is happening for any project uploaded to Polyspace Access, this needs to be investigated in more detail. Please contact MathWorks Technical Support for a deeper analysis of the issue.