MAINT: Batch integration tests - #2433
Open
jbolor21 wants to merge 1 commit into
Open
Conversation
Run integration test groups in separate pytest processes to release runner memory between batches. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
jbolor21
marked this pull request as draft
August 19, 2026 20:03
jbolor21
marked this pull request as ready for review
August 19, 2026 20:08
jbolor21
changed the title
| batch_number=0 | ||
| for test_batch in $test_batches; do | ||
| batch_number=$((batch_number + 1)) | ||
| make ${{ parameters.makeTarget }} INTEGRATION_TESTS="$test_batch" JUNIT_XML="junit/test-results-${batch_number}.xml" |
Contributor
There was a problem hiding this comment.
Rich agrees with this comment but it is copilot generated:
This loop returns only the final make command's exit status. If an earlier batch fails and a later batch passes, the Bash step succeeds, and PublishTestResults@2 does not fail the job by default. Please stop on the first failure with set -e, or collect the statuses and exit nonzero after all batches run.
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
2 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.
Description
The scheduled integration-test job can exhaust the memory available on the hosted runner. The job reached 95% memory usage and the Azure Pipelines agent stopped responding after pytest collected 222 tests, while authentication, secret retrieval, dependency setup, and token caching had already completed.
This change runs integration-test areas in sequential pytest batches. Each batch uses a fresh process, releasing accumulated test memory before the next group starts. Each batch writes a separate JUnit result file, which Azure DevOps merges when publishing results. Full integration coverage and existing reporting are preserved; end-to-end and partner-integration jobs are unchanged.