Replace 'Run time' with 'Expected Run Time' and include 'Actual Run Time' in web UI Table view?

[jonnyhtw]

Hi there,

Problem

In the example shown in the attached image, I am debugging a particular task called compile_lfric_atm and I want to see how long each failed submit is taking to fail. I know I can work this out from the start and finish times but it's a bit fiddly to work this out 'by eye'.

From chatting to @hjoliver I understand that this Run Time is actually the expected run time based on an average of cycle points however in this example I am working in the first cycle point and so it only shows me the Execution time limit: 10800.0 from the job script, i.e. 3 hours.

Proposed Solution

Replace 'Run time' with 'Expected Run Time' and include 'Actual Run Time' in web UI Table view.

Thanks,

Jonny

[hjoliver]

Useful suggestion IMO.

Expected Run Time should (as now) be the average of prior successful runs.

Actual Run Time should be job-specific and be displayed when the job finishes, success or fail.

Presumably the UI can compute this locally, from Finish - Start.