[EVO] Fix merge conflict in GsfTracking classes_def.xml#50242
Conversation
…flow for phase-2 HLT menu with tracking ntuple
…state is unavailable
… available in path length computation
This is to support the EVOLUTION branch
To support EVOLUTION branch.
To support EVOLUTION branch
…ngWrappers make `edm::Wrapper` of GsfTracking types not defined in `DataFormats` non persistable
Fix: remove dependencies of trackingNutple sequence for phase-2 HLT
Replace forward reference with Fwd.h includes for HcalDigi
Replace forward declaration with StripDigiSimLinkFwd.h include
Update the online GTs in autoCond with some frozen at 2026-02-23
Phase2-hgx365O Make V18 also using cog as the default - thus removing the error report in the ID test
…Offline Adapt `ScoutingEGammaCollectionMonitoring` to run in online DQM
Replace forward declarations with Fwd.h includes for EcalDetId
Replace forward declaration of DTuROSFEDData with Fwd.h include
Adjust TICL track linking to work with (extended) pixel tracks
…vm21-format1 [RECONSTRUCTION-XPOG] [LLVM21] Apply code-checks and formats
|
please test |
|
type evo |
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50242/48232 |
|
A new Pull Request was created by @Dr15Jones for CMSSW_16_1_EVOLUTION_X. It involves the following packages:
@AdrianoDee, @Alejandro1400, @DickyChant, @Dr15Jones, @JanChyczynski, @Moanwar, @antoniovagnerini, @arunhep, @atpathak, @battibass, @bsunanda, @civanch, @ctarricone, @francescobrivio, @ftorrresd, @gabrielmscampos, @jfernan2, @kpedro88, @makortel, @mandrenguyen, @mdhildreth, @miquork, @nothingface0, @perrotta, @rseidita, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
-1 Failed Tests: RelVals AddOn The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here:
Failed RelValsFailed AddOn Tests |
|
Good to go in evolution ib |
09728db
into
cms-sw:CMSSW_16_1_EVOLUTION_X
PR description:
Made change necessary to accommodate both code changes.
PR validation:
None