When a precise execution exits with a bad status, the driver currently dumps a confusing traceback. Instead, it should show the output status and the program's stdout text and explain that testing can't continue with a broken precise program.
(Broken precise executions can happen, for example, when we're missing the input files for a PARSEC program. The user needs to the failed execution's output to see what's going on.)
When a precise execution exits with a bad status, the driver currently dumps a confusing traceback. Instead, it should show the output status and the program's stdout text and explain that testing can't continue with a broken precise program.
(Broken precise executions can happen, for example, when we're missing the input files for a PARSEC program. The user needs to the failed execution's output to see what's going on.)