21 Sep
2012
21 Sep
'12
3:05 p.m.
Excellent. :) I had considered adding an exit code column but had avoided touching the database at first. Migration could be a little tricky. If we assume that there are few (or even zero) tools checking stdout/stderr/exit codes, then we could assume that a job failed if it had any stderr text. Then we would need appropriate backfilled exit codes - say, 0 for success and -1 for error. Would that make sense? -Scott ----- Original Message -----
Yes, it was the info section I had in mind too :)
I agree this wouldn't be needed on the normal history or peep view.
However it would also be good to show on the "bug" view for failed datasets.
(And to store it as a new column in the database for advanced queries)
Peter