-submit-job-from-previous-compilation-results
Specify that the analysis job must be resubmitted without recompilation
Syntax
-submit-job-from-previous-compilation-results
Description
-submit-job-from-previous-compilation-results specifies that
the Polyspace® analysis must start after the compilation phase, using compilation
results in a polyspace.zip file from a previous analysis. You
can use this option when a previous remote analysis stopped after the compilation
phase (potentially due to communication problems between the server and client
computers), and you need to restart the analysis, but want to avoid rerunning the
compilation. Note that you use this option with the commands in the desktop
products (polyspace-bug-finder and
polyspace-code-prover) and
not the commands in the server products (polyspace-bug-finder-server and polyspace-code-prover-server).
When you perform a remote analysis:
On the local host computer, the Polyspace software performs code compilation and coding rule checking.
The analysis job is then submitted to the MATLAB® job scheduler on the head node of the MATLAB Parallel Server™ cluster.
The head node of the MATLAB Parallel Server cluster assigns the verification job to a worker node, where the remaining phases of the Polyspace analysis occur.
If an analysis stops after completing the first step and you need to restart the analysis, this option allows you to use the compilation results from the previous analysis. You thereby avoid restarting the analysis from the compilation phase.
If you use this option, the current analysis must use the same result folder as the previous analysis and the result folder must contain a file polyspace.zip containing the compilation results from the previous analysis. Otherwise, you see an error message like this:
You used the option -submit-job-from-previous-compilation-results but the current results folder does not have compilation results.In the user interface (Polyspace desktop products only), on the Configuration pane, enter this
option in the Other field. See Other.
Examples
Specify remote analysis with compilation results from a previous analysis:
Bug Finder:
polyspace-bug-finder -batch -scheduler localhost -submit-job-from-previous-compilation-results
Code Prover:
polyspace-code-prover -batch -scheduler localhost -submit-job-from-previous-compilation-results
Tips
You cannot submit analysis jobs to a remote cluster with Polyspace as You Code™.
