TrigNavigation: fix deserializaton/thinning of Run-1 navigation
In !43270 (merged) caching of deserialized navigation blobs was implemented. However, when multiple navigation instances are used the corresponding holders also need to be cached and registered in each navigation instance.
Also throw an error in the thinning service in case the list of holders in the navigation is empty. This should never happen and would point to an issue in the initialization of the navigation.
Merge request reports
Activity
added Trigger master review-pending-level-1 labels
CI Result SUCCESS (hash 89a367ec)Athena AthSimulation AthGeneration AnalysisBase AthAnalysis DetCommon externals cmake make required tests optional tests Full details available on this CI monitor view. Check the JIRA CI status board for known problems
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
DetCommon: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 49484]removed review-pending-level-1 label
added review-approved label
mentioned in commit 2b89be02
added sweep:ignore label