CI: Tweak our nextest thread requirements #2351
Merged
Conversation
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adjusts the nextest thread requirements for VMM tests to better reflect actual resource usage patterns. The changes reduce the threads-required values for heavy and very_heavy tests and remove a separate override specifically for OpenHCL tests.
- Reduced thread requirements for
very_heavytests from 35 to 16 threads - Reduced thread requirements for
heavytests from 18 to 8 threads - Removed the dedicated override for OpenHCL tests that required 5 threads
smalis-msft
added
the
release-ci-required
Contributor
Author
|
I've run CI multiple times on this PR and things seem to be ok? We can always pull this back some in the future if we see more weirdness. |
jstarks
approved these changes
Nov 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Now that our requirements are in the right order, CI is taking significantly longer. Try scaling the requirements down a bunch.