TrigJetMonitoring Build Bugfix, 22.0 branch (2022.06.06.)
Cleaned up the build configuration of TrigJetMonitoring to fix the issue introduced in !53596 (merged).
As @tsulaia found in ATLINFR-4580, !53596 (merged) introduced an issue similar to what lead some time ago to ATLINFR-4465. The good news is that the monitoring that we've put into the nightly builds as a result of ATLINFR-4465 seems to work as intended.
The less good news is that the 22.0 builds have produced a warning for 3 days now with PROC not noticing.
At the same time kudos to @tsulaia for noticing the warning right away in master.
In the end I decided to clean up the CMake configuration of the package a bit more than what would be necessary to get rid of this problem. (Since this updated configuration should result in an every so slightly faster build.)
Merge request reports
Activity
added bugfix label
added 22.0 DQ JetEtmiss Trigger TriggerJet review-pending-level-1 labels
CI Result SUCCESS (hash 63993dee)Athena 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
DetCommon: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 53628]added review-approved review-approved-point1 labels
removed review-pending-level-1 label
removed review-approved label
added review-pending-level-1 label
added review-approved-tier0 label
removed review-pending-level-1 label
added review-approved label
mentioned in commit 5ba6fcda