-
Notifications
You must be signed in to change notification settings - Fork 185
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
Update tag for L1Trigger-L1TCalorimeter to V01-01-00 #6004
Update tag for L1Trigger-L1TCalorimeter to V01-01-00 #6004
Conversation
+externals |
The tests are being triggered in jenkins.
|
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_11_2_X/master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
Thanks, do you have an automatic way to make the |
@silviodonato , there is a jenkins job https://cmssdt.cern.ch/jenkins/job/backport-pull-request/ whcih normaly we use for back ports for data package backports this mostly fails due to conflicits. Which release cycle we need to backport this PR? |
+1 |
Comparison job queued. |
We need a backport to 11_1_X, thanks. |
Comparison is ready Comparison Summary:
|
backport failed Error: Failed to cherry-pick commits. Please backport this PR yourself.
|
Move L1Trigger-L1TCalorimeter data to new tag, see
cms-data/L1Trigger-L1TCalorimeter#22