On Tue, Jun 09, 2015 at 11:43:47AM -0400, Erik Schnetter wrote: > It is very important to catch errors from shell commands. We have basically > no error checking within the scripts, as the "set -e" is guaranteed to > catch anything unexpected. These scripts are difficult to debug since > errors are usually encountered by novices, so this kind of thorough > checking is important.
You are right. > If you temporarily need to disable error checking, then this can be done > locally, by disabling and then re-enabling error checking. This is what I did, but not locally because I wanted to trigger a recompile on jenkins to see if the error checking was indeed the problem. It was, and a proper (and hopefully working) alternative solution is already in place, assuming I caught all places where this happened. Jenkins will tell. Frank
signature.asc
Description: Digital signature
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
