Bug #14627

[crunchstat-summary] job elapsed time wrong for crunch2 jobs

Added by Tom Morris about 1 month ago.

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

0%

Estimated time:
Story points:
-

Description

The stop gap mentioned in #12748 Note-1 and implemented in 42017ce7d clearly isn't working.

For the bcl2fasq job e51c5-dz642-6ptvwlrcert9zji, crunchstat-summary reports an elapsed time of 2h8m32s while workbench reports 5h41m. For the HTML format report, two different time axes are used: 2h10m for CPU & mem but 5h40m for net:keep0.

In addition to correcting the elapsed time calculation, we should also fix the graphing so that the same aligned time base is used - at least for all metrics in a single job. We may even want to use the same time base across all jobs, but I'll leave that for a separate ticket.

Also available in: Atom PDF