Investigate periodic failures of TriggerRecordBuilderData_test

[eflumerf]

From Slack:

Michal Rigan
  4:44 AM
I've noticed that the dbt-unittest-summary.sh test, specifically TriggerRecordBuilderData_test will always fail the first time it's run in an area, and then always succeed after that:
dbt-unittest-summary.sh


/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/TriggerRecordBuilderData_test..FAILED
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/DataStoreFactory_test..........SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/HDF5FileUtils_test.............SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/DFOModule_test.................SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/HDF5Write_test.................SUCCESS

Test results are saved in /nfs/home/mrigan/dune-daq/v5.3-250226/log/unit_tests_Thu_27_Feb_11_40_35_CET_2025.log

(dbt) [mrigan@np04-srv-016 v5.3-250226]$ dbt-unittest-summary.sh


/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/TriggerRecordBuilderData_test..SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/DataStoreFactory_test..........SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/HDF5FileUtils_test.............SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/DFOModule_test.................SUCCESS
/nfs/home/mrigan/dune-daq/v5.3-250226/build/dfmodules/unittest/HDF5Write_test.................SUCCESS

Test results are saved in /nfs/home/mrigan/dune-daq/v5.3-250226/log/unit_tests_Thu_27_Feb_11_40_59_CET_2025.log
the error:
/nfs/home/mrigan/dune-daq/v5.3-250226/sourcecode/dfmodules/unittest/TriggerRecordBuilderData_test.cxx(114): ^[[4;31;49mfatal error: in "TriggerRecordBuilderData_Test/Assignments": difference{0.141165} between static_cast<double>(trbd_p->average_latency(start_time).count()){50218} and static_cast<double>(latency){57307} exceeds 5%

I've noticed this behavior as well, and consistent failures like these lead to the test being ignored.