Andrea Perrotta
Andrea Perrotta
+1 - See https://github.com/cms-sw/cmssw/pull/38968#issuecomment-1219259820
@abaty please apply the two fixes suggested by @jpata in https://github.com/cms-sw/cmssw/pull/38097#pullrequestreview-1080076974 and https://github.com/cms-sw/cmssw/pull/38097#pullrequestreview-1080077669 Since this PR only needs the reco signature, applying only those two fixes will not delay significantly...
+1 - Let have this merged, so that it can enter pre5 - Fixes in https://github.com/cms-sw/cmssw/pull/38097#pullrequestreview-1080076974 and https://github.com/cms-sw/cmssw/pull/38097#pullrequestreview-1080077669 will be applied in a forthcoming bug-fix PR
Indeed: it MUST go in master first. Backports will be taken into account only after the master version is merged and tested working
This PR is adding quite several warning lines in the logs of several workflows, for example wf1306.0: ``` %MSG %MSG-w L1TStage2uGTTiming: L1TStage2uGTTiming:l1tStage2uGTTiming@streamBeginRun 25-Jul-2022 04:05:33 CEST Run: 1 Stream: 0 Algo...
By the way, even the baseline shows for the same wf the following warning messages ``` %MSG %MSG-w L1TObjectsTiming: L1TObjectsTiming:l1tObjectsTiming@streamBeginRun 25-Jul-2022 03:32:54 CEST Run: 1 Stream: 0 Algo "L1_FirstCollisionInTrain" not...
> Hi @qliphy, @perrotta, apologies for the delay in response. Ok, this seems like it is complaining due to the L1 menu for 2016 lacking the triggers used in 17/18...
@vukasinmilosevic is there any news for the expected updates to this PR?