Skip to content

Added checking of computer resources in integtests#292

Open
bieryAtFnal wants to merge 13 commits intodevelopfrom
kbiery/check_computer_resources_in_integtests
Open

Added checking of computer resources in integtests#292
bieryAtFnal wants to merge 13 commits intodevelopfrom
kbiery/check_computer_resources_in_integtests

Conversation

@bieryAtFnal
Copy link
Contributor

Description

To help avoid confusion when the daqsystemtest integtests are run on computers that may or may not have sufficient resources (CPUs, memory, disk space), I have added checks on such resources to all of the integtests in this repo. When a computer does not have sufficient resources, the integtest is skipped. (This is accomplished by having the pytest "tests" skipped using the pytest.skip() functionality.)

To test these changes, I have run the modified integtests (typically with dbt-build --integtest) on several computers, some of which have lots of resources, and some of which don't. I considered the tests successful when either they ran cleanly or they were skipped because of insufficient resources.

It would be great for reviewers to also run these modified tests on different computers and verify similar behavior (consistent success or skipping).

Type of change

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

Testing checklist

  • Minimal system quicktest passes (pytest -s minimal_system_quick_test.py)
  • Full set of integration tests pass (daqsystemtest_integtest_bundle.sh)

Further checks

  • Code is commented where needed, particularly in hard-to-understand areas

Kurt Biery and others added 13 commits December 6, 2025 20:04
…tirun_test.py and long_window_readout_test.py.
… run_nanorc0 string from config names in the banners of tests that needed that.
… there are insufficient computer resources.
…sufficient computer resources are available.
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