You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are sample steps for demonstrating this behavior:
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
# outside of drunc:
# kill the df-01 application
# back inside drunc:
fsm drain_dataflow
fsm stop_trigger_sources
fsm stop
fsm scrap
# note the error messages printed out as part of these last several commands
exit
I've noticed that when a daq process crashes, drunc seems to encounter problems with calling the upper() function on a NoneType object.
Here is a sample of the error message that I see:
I'll post sample instructions to demonstrate this behavior next.
The text was updated successfully, but these errors were encountered: