Basically, if you set up a work area based on today's candidate release (fddaq-v5.3.1-rc1-a9) and try running unit test using the fdreadoutlibs repo checked out to its candidate release tag (v2.3.0), you'll get a couple of failures in FDReadoutRequestHandlers_test/SkipListLatencyBufferModel_DAPHNESuperChunk; things like
/cvmfs/dunedaq-development.opensciencegrid.org/candidates/coredaq-v5.3.1-rc1-a9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-13.2.0/datahandlinglibs-v3.1.2-yt76flrhxb2onb6mlc3rcroddotco5cl/include/datahandlinglibs/testutils/TestUtilities.hpp(276):
error: in "FDReadoutRequestHandlers_test/SkipListLatencyBufferModel_DAPHNESuperChunk": Fragment 'end' ts {208} is expected value {224}