Don't Print Backtrace When Unit Tests Failed

[Carltoffel]

If one test in the testing framework called by fpm test fails, the framework will likely return an exit code >0. This leads to fpm calling error stop which causes printing the backtrace in the console (at least if fpm was compiled with gfortran). This can cause some confusion, because the program did exactly what it was meant to do, but the backtrace implies something went unexpectedly wrong.

@everythingfunctional and I discussed the same behaviour in his vegetables project where he ended up with replacing error stop with stop 1. Brad tested some combinations of compiler and OS and it sounds promising as long as there aren't multiply images.

What do you think? Does the same approach applies for fpm or is there even a better way?

[LKedward]

Yes I agree, we don't need to be using error stop in fpm. I started work (LKedward@086ae55) on improving the error handling messages during compilation which would extend naturally to the case described here.