-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Disable 2022/2023 MC Tests #46843
Disable 2022/2023 MC Tests #46843
Conversation
cms-bot internal usage |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46843/42860
|
A new Pull Request was created by @AdrianoDee for master. It involves the following packages:
@AdrianoDee, @Moanwar, @DickyChant, @miquork, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
+pdmv |
@cms-sw/upgrade-l2 do you have any objection in merging this PR (it doesn't pertain to upgrade per se)? |
+Upgrade |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @mandrenguyen, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
…C_tests Disable 2022/2023 MC Tests
PR description:
This PR proposes to disable
test_MC_23_setup
andtest_MC_22_setup
given the setup is now stable and well defined and also that we moved to15_0_X
. In principle this could be back ported to14_2_X
and14_1_X
given the final production is happening in14_0_19
but, unless a problem arises (as it is with #41932), I'll just keep them.Instead of completely removing them I prefer to comment the tests just to keep track of what was the final setup (without having to dig the git history).
FYI: @makortel