[bugfix] Fix use of sched_options by the backend schedulers
#2796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes three bugs related to
sched_options. Two were introduced in 4.0 and one was present since the introduction of theuse_nodes_optionparameter.sched_optionsdue to a typo! This is fixed, unit tests are added to verify it and the configuration schema for accessing thesched_optionshas become stricter in order to avoid typos going undetected in the future.sched_optionsto be defined inside thesystemssection, as it is also stated in the docs.use_nodes_optionwhen thennum_tasks_per_nodewas not set. This bug was present since the introduction of theuse_nodes_option. Ifnum_tasks_per_nodeis not set in this case, it is considered as1.Fixes #2794.
Fixes #2795.
Fyi @smoors