Task #5651

Bug #3989: [Workbench] [DRAFT] Fix clock/node time reporting on Workbench pipeline page

Fix reported scaling factor for failed jobs (see notes)

Added by Ward Vandewege almost 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

For example, su92l-d1hrv-wo4tw2o83t7o0h8, where the scaling factor (and compute time used by the failed job) keeps increasing.

History

#1 Updated by Ward Vandewege almost 4 years ago

  • Description updated (diff)

#2 Updated by Brett Smith almost 4 years ago

  • Category set to Workbench
  • Story points set to 0.5

app/views/pipeline_instances/_running_component.html.erb sums the runtime of each component task. If the task doesn't have its finished_at attribute set, the code uses Time.now. That code should probably fall back to the job's finished_at if that's set.

We may also want to see about ensuring each task's finished_at is set in crunch-job, although I think there's at least one theoretical corner case where it's not supposed to be. (Just off the top of my head—I might be misremembering.)

#3 Updated by Tom Clegg almost 4 years ago

  • Tracker changed from Bug to Task
  • Subject changed from [Workbench] Workbench misreports scaling factor for failed jobs to Fix reported scaling factor for failed jobs (see notes)
  • Parent task set to #3989

Also available in: Atom PDF