No indication of what happened when TCMaker throws an exception #320
Description
The steps listed below recreate a problem in which the tc-maker-1 process dies because there is a missing configuration parameter. The reason that I'm filing this Issue is that, when this happens, there is nothing in the application log files that indicate that the TriggerCandidateMaker threw an exception that was not handled (here). When I do a test run, the tc-maker-1 process just silently goes away. Why isn't there more of an indication of what happened?
Maybe I answered my own question when I said "unhandled exception". If the application framework has no way to indicate what happened in this case, I'll add an ers::error call immediately before the TCM code throws the exception so that in the future, we'll have at least a little indication of what happened.
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_250226_A9 ${DATE_PREFIX}FDDevTest_${TIME_SUFFIX}
cd ${DATE_PREFIX}FDDevTest_${TIME_SUFFIX}/sourcecode
git clone https://github.com/DUNE-DAQ/appmodel.git -b develop
git clone https://github.com/DUNE-DAQ/daqsystemtest.git -b develop
git clone https://github.com/DUNE-DAQ/dfmodules.git -b develop
git clone https://github.com/DUNE-DAQ/trigger.git -b develop
git clone https://github.com/DUNE-DAQ/triggeralgs.git -b kbiery/tcmaker_avoid_crash
cd ..
sed -i 's/.*The output TC type name.*//' sourcecode/appmodel/schema/appmodel/trigger.schema.xml
dbt-workarea-env
dbt-build -j 12
dbt-workarea-env
daqconf_set_connectivity_service_port local-1x1-config config/daqsystemtest/example-configs.data.xml
mkdir rundir
cd rundir
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml local-1x1-config boot --no-override-logs wait 5 conf wait 3 start --run-number 101 enable-triggers wait 10 disable-triggers drain-dataflow stop-trigger-sources stop scrap terminate
egrep -i 'error|warn' log*.txt