-
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
Features needed for CMSSW_10_1_1 #22865
Comments
A new Issue was created by @fabiocos Fabio Cossutti. @davidlange6, @Dr15Jones, @smuzaffar, @fabiocos can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
For TSG we request: 10_2_X/10_2_0_pre1 10_1_X/10_1_1 |
@arunhep @lpernie Huston we have a problem... After the integration in 10_2_X of the GT PR #22833 (whose backport #22834 should be one of the key residual ingredients for 10_1_1) we are getting several failures in tonight's IB, see for instance They are reproducible, do not appear if only the GT PR is not used (In any case the other additions tonight look unrelated to this), and have the pattern %MSG A test on some of the failing workflows is running in #22834 to cross check that this appears also in the 10_1_X branch. Any clue of what is wrong/missing? Needless to say that this is a show-stopper for 10_2_0_pre1 and 10_1_1 if not solved. |
@fabiocos i know the problem. i will open a PR soon. |
@fabozzi the new datasets look all at CERN, so I expect we should have no failures due to missing inputs |
At this point I will freeze the present situation, more additions may come in a following patch/release |
The validation of CMSSW_10_1_0 is ongoing, we already know that we need to back-port some fixes and some last minute planned additions. The target is a CMSSW_10_1_1 containing features already deployed and to be validated in 10_2_0_pre1 (the build and validation of these two releases will have to move unfortunately in parallel).
(Updated on April 7 23:00)
Here is the list of the PRs already backported from 10_2_X as fixes:
#22822 from cms-tsg-storm: Fix l1 emulation in HLT scripts (101X)
#22823 from folguera: BugFix for L3MuonCandidateProducerFromMuons
#22819 from bsunanda: Run2-alca126 Add eta dependent threshold for ECAL
#22818 from mmusich: [10.1.X] fix segmentation fault in SiStripBadComponentInfo (backport)
#22792 from thomreis: Fix L1T muon copy comparison DQM harvesting path - 101x
#22791 from mmusich: [10.1.X] remove useless triplication of AAG data in calibTree
#22800 from hroskes: fix preexisting tracker alignment validation
This issue is meant to collect the other features that are really necessary for the operations at the beginning of data taking and for the completion of the PF calibration.
The list that I am aware of at present is:
Please add further motivated requests to this issue
The text was updated successfully, but these errors were encountered: