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
separate numbering for 2017 and 2023 workflows #15817
Conversation
A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_8_1_X. It involves the following packages: Configuration/PyReleaseValidation @cmsbuild, @srimanob, @davidlange6, @hengne, @fabozzi can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@piperov |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
|
+1 |
10424.0, #2023D1 ttbar (Run2 calo) | ||
11224.0, #2023D3 ttbar (HGCal) | ||
20424.0, #2023D1 ttbar (Run2 calo) | ||
21224.0, #2023D3 ttbar (HGCal) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The workflow list is incorrect or the numbering has to be redone
20424.0 is TTbar_13TeV_TuneCUETP8M1_2023D2
and 21224.0 does not exist.
It should be 20024.0 and 20824.0 based on the numbering generated (I'm relying on CMSSW_8_1_X_2016-09-13-1100)
Due to an increasing number of conflicting upgrade PRs (#15662, #15613, #15805, with more coming), it was decided to separate the numbering for 2017 and 2023 workflows. The authors of the above PRs will have to rebase once this PR is merged.
The separate numbering is implemented by adding a new dimension to the dictionaries used to construct the upgrade workflows. This foresees possible expansions, e.g. using 30000 for 2019 workflows.
attn: @davidlange6