Bug #10516
Updated by Tom Morris over 7 years ago
In looking at this job: https://workbench.e51c5.arvadosapi.com/pipeline_instances/e51c5-d1hrv-23r02rmoqfq5tew I see a couple of things misleading about the times being reported: The - the amount of time the job was queued appears to be computed using the current time causing it to continue to increase even long after the job completed - the node scaling is reported as "1.0x" even though the CWL scattered across a large number of parallel nodes. The time from the workunit needs to be propagated up to the top level. Work unit stats need to be calculated recursively? nodes