Modified the 3ru_3df_multirun_test to make use of the 'start-run' command...

[bieryAtFnal]

…for one of its three runs. This will validate the use of that command going forward.

Description

At today's SWI&T meeting, Michal mentioned that he noticed that the start-run command in run control was running boot and conf when those transitions had already been run in the current DAQ session.

Surprisingly, we don't seem to have an integration test that uses start-run, but we certainly should.

This PR makes use of that command in one of the three data-taking runs that are part of the 3ru_3df_multirun_test.

The modified version of this integtest will (and should) fail until the bug is found and fixed in run control.

Type of change

• Optimization (non-breaking change that improves code/performance)

Testing checklist

• Full set of integration tests pass (dunedaq_integtest_bundle.sh)
  • NB, this test will fail initially and that is a good thing. The failure demonstrates a problem in run control.

[MRiganSUSX]

Thank @bieryAtFnal.

Can confirm that:

• running 3ru_3df_multirun_test the errors are caught

(although not directly mentioned in this Failures end block (?))

• running with drunc @ DUNE-DAQ/drunc#1015 which is the fix targetting this, there are no more errors

[bieryAtFnal]

@MRiganSUSX , thanks for your review. I'm going to go ahead and merge these changes to the develop branch, and I've created an Issue in the integrationtest repo to request that we make the text in the 'failure end block' more useful (DUNE-DAQ/integrationtest#170).