ATR-28617: Rename FS LRT sequence to avoid clash with FS VSI
In pure CA trigger configuration, the unconventional tracking FS VSI chain was losing its VSI algorithm (ATR-28617). This seems to be traced to a sequence name overlap where the FS LRT chains erroneously generated a duplicate sequence called 'UncFSVSIreco' that did not contain this alg. Renaming this sequence restores the correct behaviour in a menu containing both sets of chains.
Noting that this seems to be a possible vulnerability, likely in the control flow generation, where non-unique sequence names could interfere across the menu. If there is a clear solution (@fpastore might be able to advise?) it could be integrated into this MR, otherwise would be a priority to follow up.
Merge request reports
Activity
This merge request affects 1 package:
- Trigger/TriggerCommon/TriggerMenuMT
This merge request affects 2 files:
- Trigger/TriggerCommon/TriggerMenuMT/python/HLT/Config/ControlFlow/HLTCFConfig.py
- Trigger/TriggerCommon/TriggerMenuMT/python/HLT/UnconventionalTracking/FullScanLRTTrackingConfiguration.py
added Trigger TriggerMenu main review-pending-level-1 labels
CI Result SUCCESS (hash a09953c9) Athena externals cmake make 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
For experts only: Jenkins output [CI-MERGE-REQUEST-EL9 3297] added review-approved label and removed review-pending-level-1 label
mentioned in commit 1ae2a4ef