Repository navigation
Added support for multiple TRACE debug levels for a given TRACE_NAME in integtests... - #173
Merged
Merged
Conversation
…ME in the trace_debug_settings fixture.
2 tasks done
eflumerf
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
... and, added error checking for the value specified in the
trace_debug_levelsintegtest config param.Description
When I recently tried to set two TRACE levels (e.g. level 10 and level 13) for a given TRACE_NAME (e.g.
DefaultRequestHandlerModel.hxx) in an integtest file, I realized that the initial support for setting TRACE debug levels in our integtest files did not handle more than one level. The changes in this PR remedy that situation.I also added error checking for the contents of the
trace_debug_levelsintegtest config parameter. With these changes, users should get notified when various types of invalid values have been specified.It will be useful to test these changes in conjunction with DUNE-DAQ/dfmodules#516, and the following suggested instructions make use of those changes:
Type of change
Testing checklist
dunedaq_integtest_bundle.sh)Further checks