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
Release 2.2.0
After caper init sge, I add a custom parameter to sge_resource_param. Upon caper run, the generated backend.conf has the hard-coded default sge_resource_param, not the custom one.
I've isolated the problem to the init of the CaperRunner object in cli.py
and to each of the manager merge_dict in caper_backend_conf.py.
The new resource_param feature was added only for slurm, but none of the other managers. If I caper init slurm and add a custom parameter to slurm_resource_param, it does override the default in the init of CaperRunner and I see the change in backend.conf
Release 2.2.0
After
caper init sge
, I add a custom parameter to sge_resource_param. Uponcaper run
, the generated backend.conf has the hard-coded default sge_resource_param, not the custom one.I've isolated the problem to the init of the CaperRunner object in cli.py
caper/caper/cli.py
Lines 238 to 248 in c10d05b
merge_dict
in caper_backend_conf.py.The new
resource_param
feature was added only for slurm, but none of the other managers. If Icaper init slurm
and add a custom parameter to slurm_resource_param, it does override the default in the init of CaperRunner and I see the change in backend.confHave to add the manager
resource_param
to each of the managermerge_dict
in caper_backend_conf.py like is done for slurm.The text was updated successfully, but these errors were encountered: