When running wbi remote command, we should have an option of running them interactively or just logging the job id and being done with it. This PR adds this.
There are some simplifications when monitoring the job (if running interactively) - we can/should use srun in such cases instead of sbatch.
The other code tweaks here have to do with specifying --time=... flag for srun and sbatch. srun insists that we specify it, so we pass on the responsibility to the user of the wbi remote command. This will also override the defaults in the sbatch case. Otherwise, the defaults specified in the relevant template files are used.
When running
wbi remotecommand, we should have an option of running them interactively or just logging the job id and being done with it. This PR adds this.There are some simplifications when monitoring the job (if running interactively) - we can/should use
srunin such cases instead ofsbatch.The other code tweaks here have to do with specifying
--time=...flag forsrunandsbatch.sruninsists that we specify it, so we pass on the responsibility to the user of thewbi remotecommand. This will also override the defaults in thesbatchcase. Otherwise, the defaults specified in the relevant template files are used.