On Wed, Apr 21, 2010 at 01:58:40PM -0400, Nate Coraor wrote:
Ry4an Brase wrote:
If you're employing a shell script wrapper around your tool in the tool runner, as many seem to do, you can just add "2>&1" to the end of your command.
Hi Ry4an,
While this would indeed fix the problem of the job failing, it'd prevent any failures from ever being detected. What we've done for tools that don't set a return code is attempt to parse the output for errors.
Absolutely. I was suggesting squelching stdout only for his tool specifically because he says he does return a valid exit code on error. It's certainly not a good general solution, though. Having a tag in the <tool>...</tool> config files which indicates what counts as an error (a) nothing, (b) non-zero exit, (c) text on stdout, or (d) either, with D being the default might be a nice addition in the future. -- Ry4an Brase 612-626-6575 University of Minnesota Supercomputing Institute for Advanced Computational Research http://www.msi.umn.edu