Open brianmcmichael opened 7 years ago
I think that the adapters all implement this method. Verify that by looking at the ood_core code. If it looks legit, do this feature.
This can move forward for torque
slurm
and pbspro
. The only other adapter at present that has extended view (LSF) does not yet have this.
Don't know why I thought lsf
doesn't have support for this - it did and still does:
So in any case, for any implementer of this good first issue
-
The line in question that needs updated is here (for torque) in the extended_data_torque
method. There will be similar methods for the other schedulers as well. It seems we'd need to support these 4 schedulers: torque, slurm, pbspro and lsf.
Currently the wallclock times are derived via accessing native attributes, like:
attributes.push Attribute.new "Walltime", (info.native.fetch(:Resource_List, {})[:walltime].presence || "00:00:00")
These can be replaced with something like:
attributes.push Attribute.new "Walltime", info.wallclock_limit || "00:00:00"
After updating to the the latest
ood_core
release.┆Issue is synchronized with this Asana task by Unito