Open brianmcmichael opened 7 years ago
I like this idea, do you happen to know what job adapters this would work for?
Presumably this would be now - info#submission_time
or info#dispatch_time - info#submission_time
. Some adapters (https://github.com/OSC/ood_core/search?q=submission_time&unscoped_q=submission_time and https://github.com/OSC/ood_core/search?q=submission_time&unscoped_q=dispatch_time) might not support this fully or for all jobs (does it work when submitting job arrays?).
Other edge cases might include: dispatch_time is not available but submission_time is and the job is running...
Basically if you do dispatch_time.to_i
and it doesn't return a reasonable value (like 0 is not reasonable).
This can be a row added to the table in the details section.
Other edge cases might include: dispatch_time is not available but submission_time is and the job is running...
We only need queued time for queued jobs or for all the jobs? @ericfranz
reviewed; still a great idea
For jobs that are currently in queue, activejobs should show the amount of time a job has been waiting in that state.
┆Issue is synchronized with this Asana task by Unito