test: preserve machine gate settings when pinning run models - #1615
Closed
santoshkumarradha wants to merge 2 commits into
Closed
santoshkumarradha wants to merge 2 commits into
santoshkumarradha wants to merge 2 commits into
Conversation
santoshkumarradha
marked this pull request as ready for review
September 27, 2026 16:59
This was referenced Sep 27, 2026
Member
Author
|
Superseded by the consolidated draft #1627. Exact reviewed head |
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.
Three run-model tests replaced the complete profile after the shared fixture disabled machine load and memory gates. On a busy host this silently restored the default load limit, so the scripted jobs never started and timed out.
Apply model pins through the settings API, preserving the fixture's resource settings. This only changes test setup. Partially addresses #1525.
Spark evidence: unchanged base 837b2b0 reproduces the load refusal in 61.486 seconds; with the fix all three affected tests pass in 5.736 seconds while sharing the same loaded host. Final
make pr-readypassed on Spark at53877754b, including the complete affectedcmd/codeafsuite in 233.832 seconds. CI run 36334534140 is green. No product runtime changed, so this fixture correction requires no separate model-driven workflow. Separate cleanup-race failures are investigated in #1616 and #1612; they are not masked by this change.