Also consider it a crash if doComparison is False and the return code is non-zero

[atmyers]

We apparently don't consider a non-zero exit code a failure unless self.run_as_script is True. When doing plotfile comparisons, this isn't a big issue, since the comparison itself will fail as the test did not produce any output. However, when we run through travis we turn off comparisons, so we need to check the exit code.

An alternative fix would be to consider all non-zero exit codes a failure. In principle I prefer this, but I don't know the reasoning behind the original behavior here, so I'd like to be conservative.

[ax3l]

Thank you! :)

[ax3l]

for a follow-up: As @atmyers outlined above, I would also prefer to consider all non-zero exit codes, in good unix manner, an error.
Shall we try this @RemiLehe @MaxThevenet?
We probably just have to check that WarpX' executables return 0 on --help|-h and non-zero on input file errors, etc.