This is an intended change to the behavior of Code Prover analysis introduced in R2017a. In that release, the default behavior was changed to allow analysis to continue to any remaining files if a compilation failure is detected. Hence, reports may be generated even if a compilation failure occurs.
Prior to R2017a, the default behavior was to stop analysis if any compilation failure was detected. To restore the old default behavior, you may specify the '-stop-if-compiler-error' option flag via the command line or in the Environment Settings page.
For more information on the compiler error flag option, please refer to the link below:
Make sure that both the bug finder and the report generator are from R2018b. It is possible for the bug-finder and the report-generator to be referencing different versions of Polyspace. This has been known to prevent a report from being generated.
Best Answer