Clear Filters
Clear Filters

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

11 views (last 30 days)
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,

Accepted Answer

Andreas Apostolatos
Andreas Apostolatos on 25 May 2021
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,
Kind regards,

More Answers (1)

Anirban on 8 Apr 2021
Edited: Anirban on 9 Apr 2021
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
Narayan Narvekar on 12 Apr 2021
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,
Anirban on 12 Apr 2021
Edited: Anirban on 12 Apr 2021
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.

Sign in to comment.


Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!