Job's referenced from via JobRef don't have their statistic's updated

[gschueler]

When a job is referenced via a jobref, the statistics are not updated when they run by a parent.

original LH ticket

Original Creator: Noah Campbell

[gschueler]

(by Greg Schueler at 2010-11-18T15:51:27-08:00)

deferring for future release..

from irclog:

gschueler

3:42 well the problem is that when you run a jobref, it doesn't really run the job..it just runs the workflow for the job

3:43 i.e. there is no "Execution" associated with that job

noahcampbell

3:43 We can bump this out to a later revision

3:44 I just noticed that a particular job of significance was being called many many times through a jobref and there were no job stats. This makes it look like it's not being used

gschueler

3:45 ok…i think we'd either have to modify Execution to allow some kind of chained Execution (which has no output file of its own), or update the way stats are calculated so that the successrate is stored in the ScheduledExecution

3:45 right now it just queries for number of successful Executions

[siliconcow]

+1 This would be really helpful to us. We have long workflows and we can't tell what step they're at, how often each step is failing, which step is making the entire workflow take longer, etc.