-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add resource tracking to the test harness #29583
Labels
Comments
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 19, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 19, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 19, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 20, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 20, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 20, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 20, 2024
loganharbour
added a commit
to loganharbour/moose
that referenced
this issue
Dec 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
We have resource contention with running jobs on CIVET. We should track resource usage (cpu, memory) in order to set restrictions on tests on a per-test basis.
Design
Poll for resident memory and CPU usage for each test within the
TestHarness
.Impact
Better experience for a shared environment for CIVET, will assist users in creating tests with smaller resource footprints.
The text was updated successfully, but these errors were encountered: