Skip to content

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. 😦

image

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