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
When generating a sample config file, there are two issues:
the [job] section lists the options as job-<option>, which causes the option loader to interpret each of these options as job-job-<option>.
For example, the backend-config option is output as: job-backend-config in the [job] section. When setting it (and uncommenting it), easybuild throws this error: ERROR: Failed to parse configuration options: 'parseconfigfiles: no option corresponding with opt job-backend-config dest job_job_backend_config in section job'. Modifying the config file and changing job-backend-config to backend-config fixes the problem. The job- prefix for options in the [job] section should not be there.
The job-backend option is in the [config] section instead of in the [job] section. This isn't causing any breakage, but is potentially confusing.
The text was updated successfully, but these errors were encountered:
job-backend in the config section is kind of deliberate, since it's a general configuration parameter, rather than something specific to the jobs being submitted... I agree it's potentially confusing though.
When generating a sample config file, there are two issues:
[job]
section lists the options asjob-<option>
, which causes the option loader to interpret each of these options asjob-job-<option>
.For example, the
backend-config
option is output as:job-backend-config
in the[job]
section. When setting it (and uncommenting it), easybuild throws this error:ERROR: Failed to parse configuration options: 'parseconfigfiles: no option corresponding with opt job-backend-config dest job_job_backend_config in section job'
. Modifying the config file and changingjob-backend-config
tobackend-config
fixes the problem. Thejob-
prefix for options in the[job]
section should not be there.job-backend
option is in the[config]
section instead of in the[job]
section. This isn't causing any breakage, but is potentially confusing.The text was updated successfully, but these errors were encountered: