Skip to content

Changes to support integration test verbosity levels#312

Open
bieryAtFnal wants to merge 8 commits intodevelopfrom
kbiery/integtest_verbosity_level_ideas
Open

Changes to support integration test verbosity levels#312
bieryAtFnal wants to merge 8 commits intodevelopfrom
kbiery/integtest_verbosity_level_ideas

Conversation

@bieryAtFnal
Copy link
Copy Markdown
Contributor

These changes are intended for the fddaq-v5.7.0 software release.

Description

In discussions of possible improvements to our regression/integration tests, it was suggested to provide several different levels of verbosity. These changes are part of implementing those, and this PR is best tested and merged with DUNE-DAQ/integrationtest#152. The integrationtest PR has some details about the changes.

In this repo, there were a few changes that were made in addition to the ones needed for verbosity levels. Those include the following:

  • configuration names in integtests that had "Software_TPG" in their name have been modified to say WIBEth_TPG or DAPHNE_TPG since all TPG is software-based these days
  • most, if not all, integtests have been modified to make use of the new basic_checks common function for verifying successful running of the integrationtest fixtures
  • a couple of unneeded hostname checks in example_system_test have been removed
  • the sample_ehn1_multihost_test was modified so that it can be successfully run from a base release
  • in the dunedaq_integtest_bundle.sh script,
    • command-line options were added for verbosity level and full run-control output (--verbosity and --trigger-full-rc-output)
    • the concise-output command-line option was re-mapped to correspond to --verbosity 1

Please see the suggested instructions for testing these changes in DUNE-DAQ/integrationtest#152.

Type of change

  • New feature or enhancement (non-breaking change which adds functionality)

Testing checklist

  • Full set of integration tests pass (dunedaq_integtest_bundle.sh)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants