FIx default value for processing version

[vkuznet]

Fixes #10844

Status

ready

Description

Change default values of processingVer in various places of WMCore codebase

Is it backward compatible (if not, which system it affects?)

MAYBE

Related PRs

Complement to #11043

External dependencies / deployment changes

[vkuznet]

Alan, turns out WMCore has plenty of processingVer defaults pointed to None. I scan WMCore code for them, based on jenkins test failures and I think I identified the final set, unless the default values of processingVer at a different lines. Please include this PR in jenkins tests and we will see how it is going.

[cmsdmwmbot]

Jenkins results:

• Python3 Unit tests: succeeded
  • 7 tests added
  • 1 changes in unstable tests
• Python3 Pylint check: failed
  • 12 warnings and errors that must be fixed
  • 6 warnings
  • 101 comments to review
• Pylint py3k check: succeeded
• Pycodestyle check: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/12966/artifact/artifacts/PullRequestReport.html

[amaltaro]

Thanks Valentin. Tests are still running.

As discussed in our weekly meeting last Monday, pull requests do not get added to the quarterly GH project (only GH issues), so I'm removing it. The "BUG" label doesn't need to be added to the code changes as well, it's usually set only for the issue.

[vkuznet]

Alan, thanks for corrections, I still need to get use to the rules, I did it automatically without thinking too much :) Meanwhile, the pylint test fails but not due to changes I made and I feel uncomfortable to change code based on proposed pylint suggestions as it is not related to the fix. Please clarify if pylint changes will still be needed.

[amaltaro]

Thanks, Valentin! We are back to 45 permanent failures in the oracle baseline unit tests.