Certain errors do not result in a non-zero exit code

[VincentVanlaer]

There are some errors that stop GYRE immediately, but do not make GYRE return a non-zero exit code (everything that ends up calling stop). This makes it more difficult to detect whether something has gone wrong when running GYRE in a batch. In my case this was due to multiple GYRE instances access a tar_fit file at the same time (which I believe is fixed by 0d246244f87ae83139972ceb374c40c11f515a87), which caused $ABORT and stop 'Program aborted' to be called.