When job-cost.sh runs on external servers (e.g. build nodes attached from 3rd party labs), it does not exit 0, which causes all builds to be marked as unstable. Since these are valid build machines, it should not assume that any failure is an error.