On Friday, September 21, 2012, Scott McManus wrote:

> Just to be clear, whenever a tool's <stdio> rules are triggered
> there should be messages prepended to stdout and/or stderr.
> If a tool defines a <stdio> regular expression and the regular
> expression matches on stdout, a message should be prepended to
> stdout. However, these will be empty if tools without <stdio>
> sections fail (which is true for most tools at this time).
> What you're asking for is to include the return code in the history
> panel. It might make more sense to include this kind of information
> in the View Details (which you get by clicking on the job name
> and then clicking the "i" button). That way there's less clutter
> and it's still easy to get to failures (which hopefully aren't
> happening very often). What do you think?
> -Scott
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)

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:


Reply via email to