Repository navigation
Minor changes for debugging DFO stop timeouts - #523
Open
bieryAtFnal wants to merge 8 commits into
Open
bieryAtFnal wants to merge 8 commits into
bieryAtFnal wants to merge 8 commits into
Conversation
…nabled TRACE levels in large_trigger_record_test.py for debugging DFO stop behavior.
…e_test and large_trigger_record_test integtests.
bieryAtFnal
marked this pull request as ready for review
November 10, 2026 22:12
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.
Description
Added a
DataWriterOpMon metric for the maximum time that is spent writing aTriggerRecord.Also, modified the
insufficient_disk_space_test.pyandlarge_trigger_record_test.pyintegtests so that they enable useful TRACE debug messages.Also, modified the
large_trigger_record_test.pyso that it uses a DFO stop timeout of 10 seconds. The goal of that change is to help make the stopping of a run more likely to succeed without experiencing DFO stop timeouts or TriggerRecordToken message leakage between runs.In general, these changes were in response to my debugging of DFO timeout error messages and Token message leakage between runs seen in the two integtests mentioned above when they are run on np04-srv-019.
Type of change
Testing checklist
dbt-build --unittest)pytest -s minimal_system_quick_test.py)dunedaq_integtest_bundle.sh)Further checks