Fix a single misuse of flagged conditions
Breaking off parts of !40082 (closed) to make it manageable
SCT_FlaggedCondData
is the default name in offline, but SCT_FlaggedCondData_TRIG
is for HLT. Naturally any single incorrect instance of this (such as the example here) arises somewhere in a few layers of default-constructed tools.
Have attempted to rationalise this one instance, but it's still not great.
Merge request reports
Activity
added InnerDetector Trigger master review-pending-level-1 labels
CI Result SUCCESS (hash d1375dff)Athena AthSimulation AthGeneration AnalysisBase AthAnalysis externals cmake make required tests optional tests Full details available on this CI monitor view
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
AthGeneration: number of compilation errors 0, warnings 0
AnalysisBase: number of compilation errors 0, warnings 0
AthAnalysis: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 28301]added review-approved label and removed review-pending-level-1 label
mentioned in merge request !40082 (closed)
mentioned in commit 8a8802a8
added sweep:ignore label