The stop_trigger_sources transition can take multiple minutes in a simple demo system #216
Description
I'm not sure whether this repo (fdreadoutlibs) is the right place to file this Issue, but I wanted to document the fact that the stop_trigger_sources transition often takes ~2 minutes to complete when using the simple system configuration that is currently available in the appmodel repo and a recent nightly build of the software.
Here are sample steps to demonstrate the issue:
DATE_PREFIX=`date '+%d%b'`
TIME_SUFFIX=`date '+%H%M'`
source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
setup_dbt latest_v5
dbt-create -n NFD_DEV_240820_A9 ${DATE_PREFIX}20AugNightlyFDv5Test_${TIME_SUFFIX}
cd ${DATE_PREFIX}20AugNightlyFDv5Test_${TIME_SUFFIX}/sourcecode
git clone https://github.com/DUNE-DAQ/appmodel.git -b develop
cd appmodel ; git checkout 4e34d68adc4; cd ..
git clone https://github.com/DUNE-DAQ/fdreadoutlibs.git -b develop
cd fdreadoutlibs; git checkout ab0d71cc4f9; cd ..
git clone https://github.com/DUNE-DAQ/fdreadoutmodules.git -b develop
cd fdreadoutmodules; git checkout 105a58f82cc2; cd ..
cd ..
sed -i 's/unpack_one_register(second_half)/unpack_one_register(first_half)/' sourcecode/fdreadoutlibs/include/fdreadoutlibs/wibeth/tpg/FrameExpand.hpp
dbt-workarea-env
dbt-build -j 12
dbt-workarea-env
mkdir rundir
cd rundir
# Execute the following commands by hand:
killall drunc-controller
drunc-unified-shell ssh-standalone
# within drunc
boot test/config/test-session.data.xml test-session
fsm conf
fsm start run_number 101
fsm enable_triggers
# wait for a few seconds
fsm disable_triggers
fsm drain_dataflow
# note how long the next step takes
fsm stop_trigger_sources
fsm stop
fsm scrap
exit
I believe that this long interval was not present in nightly builds as recent as 17-Aug.