Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--confighelp generates job-* options incorrectly #329

Closed
pol opened this issue Apr 13, 2017 · 2 comments
Closed

--confighelp generates job-* options incorrectly #329

pol opened this issue Apr 13, 2017 · 2 comments

Comments

@pol
Copy link
Contributor

pol commented Apr 13, 2017

When generating a sample config file, there are two issues:

  1. 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.

  1. 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.
@boegel
Copy link
Member

boegel commented Apr 18, 2017

Thanks for reporting this @pol.

This is (mostly?) a duplicate of easybuilders/easybuild-framework#1331, and it should be fixed in vsc-base, cfr. hpcugent/vsc-base#211

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.

@pol
Copy link
Contributor Author

pol commented Jun 20, 2017

I agree that this is essentially the same issue. I shall close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants