Fix when unschedule mode and customise_command are used together #6492
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.
customise_commands will fail in unschedule mode because it's called before the module is load.
https://github.com/cms-sw/cmssw/blob/CMSSW_7_2_X/Configuration/Applications/python/ConfigBuilder.py#L2211-L2226
For example,
cmsDriver.py step3 --filein file:MUO-Phys14DR-00003_step2.root --fileout file:MUO-Phys14DR-00003.root --mc --eventcontent MINIAODSIM --runUnscheduled --datatier MINIAODSIM --conditions PHYS14_25_V1 --customise_commands 'process.patJetPartons.partonMode = cms.string("Pythia6")' --step PAT --python_filename MUO-Phys14DR-00003_3_cfg.py --no_exec --customise Configuration/DataProcessing/Utils.addMonitoring -n 20