On Mon, Dec 2, 2013 at 12:01 PM, Andrew Clegg <[email protected]> wrote: > > I would tend to agree that this might not be the most robust way of doing > this. > I guess there could be other situations where writing would fail during the > actual job execution, but work during output preparation -- e.g. too many open > files during execution.
I have yet to see a situation where GNU Parallel did not do the Right Thing in those situations. If you can create a situation where it does not, then let us have a look at that. > Would it be better to keep track (in memory) of the return codes from the > individual jobs, and if any are non-zero, print a warning to stderr along with > a summary of the failed ones? > > Something like: > > Warning: 3 jobs returned non-zero exit status > zcat 2013-01-01-01.gz returned 1 > zcat 2013-01-01-02.gz returned 1 > zcat 2013-01-01-03.gz returned 1 That I do not like. If the user is interested in the number of failing jobs, he should look at $? which contains this information. See http://www.gnu.org/software/parallel/man.html#exit_status If the user is interested in which jobs failed, he should use --joblog. /Ole
