You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ireed based on our discussion in the HPC validation mini series, you mentioned the need for auto-generating configuration such as slurm partition that can just be picked up by buildtest.
I think this feature request is reasonable.
We need to auto-generate executors for all executor types i take it local, slurm, lsf, pbs, cobalt. Potentially we can have a command buildtest config executors discover that can detect new executors, now we can have buildtest automatically update the configuration file.
I take it if an executor is already defined, then down redefine a new executor
The text was updated successfully, but these errors were encountered:
@shahzebsiddiqui the main thing that needs to be detected for cloud systems is the specs. For a given node, i dont know things such as the expected number of cores, gpus, interconnects etc. Commands such as lshw may not be reliable due to potential HW failure and hypervisor issues.
@ireed based on our discussion in the HPC validation mini series, you mentioned the need for auto-generating configuration such as slurm partition that can just be picked up by buildtest.
I think this feature request is reasonable.
We need to auto-generate executors for all executor types i take it
local
,slurm
,lsf
,pbs
,cobalt
. Potentially we can have a commandbuildtest config executors discover
that can detect new executors, now we can have buildtest automatically update the configuration file.I take it if an executor is already defined, then down redefine a new executor
The text was updated successfully, but these errors were encountered: