Bug #10177

Confusing job duration reporting

Added by Tom Morris almost 3 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
10/01/2016
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

These two sentences make no sense: "This pipeline started at 1:45 PM 10/1/2016. It completed in 20h33m at 3:16 PM 10/1/2016."

The rest of the job details are below, but presumably this is some kind of artifact of job reuse. As a job submitter, the things I'm interested in are: elapsed time and cost. Core hours are probably a reasonable proxy for cost. Node hours less so, because the nodes can vary greatly in size (number of cores) and cost. I'm also interested in seeing which jobs were reused, primarily to see if it matches with my expectations.

------
It ran for 20h33m and used 22h49m of node allocation time (1.1тип scaling).

Complete
uuid: bd44f-d1hrv-m0jcnjblafskza5
modified_by_user_uuid: Ward Vandewege
created_at: 1:45 PM 10/1/2016
started_at: 1:45 PM 10/1/2016
finished_at: 3:16 PM 10/1/2016

History

#1 Updated by Tom Morris almost 2 years ago

  • Target version set to Arvados Future Sprints

Also available in: Atom PDF