Lots of warning messages when running 3ru_3df_multirun_test.py about trigger HOT 7 CLOSED

I think the "Trigger Matching result with empty fragment" errors are coming from TCs arriving not in time order, and should be fixed by the two PRs:

DUNE-DAQ/readoutlibs#24
#126

I'm still working on the "tardy input set" errors

from trigger.

With the N22-05-23 Spack nightly, I'm still seeing the following warning messages:

22-May-23 08:50:25,337 WARNING [bool dunedaq::trigger::TriggerZipper<TSET>::proc_one() [with TSET = dunedaq::trigger::Set<triggeralgs::TriggerActivity>] at /tmp/root/spack-stage/spack-stage-trigger-N22-05-23-jzcm4ucluzztjfwbdouocthr4jnbezbx/spack-src/plugins/TriggerZipper.hpp:217] Tardy input set from region 1 element 0. Set start time 79554162208950000 but last sent time 79554162213720000 DAQModule: tazipper

from trigger.

Do you see a lot of those messages, or just a few?

from trigger.

Lots.

from trigger.

I was not able to fix this in time for 3.0, so we've worked around it in the dfmodules integration tests: DUNE-DAQ/dfmodules#189

from trigger.

I think these are fixed by the combination of #133 and DUNE-DAQ/daqconf#101

from trigger.

The changes in trigger and daqconf that fix this have been merged, so closing.

from trigger.