[8.19] [ML] Run QA and PyTorch suites concurrently in a single triggered build (#3131) - #3134
Open
edsavage wants to merge 1 commit into
Open
[8.19] [ML] Run QA and PyTorch suites concurrently in a single triggered build (#3131)#3134edsavage wants to merge 1 commit into
edsavage wants to merge 1 commit into
Conversation
…lastic#3131) Manual 8.19 backport of elastic#3131. The auto-backport conflicts because 8.19 lacks the "Upload ES inference tests x86_64" step that sits adjacent to the QA-trigger block on main, so the hunk context cannot anchor. Consolidates the separate run_qa_tests / run_pytorch_tests upload steps into a single trigger with a comma-separated QAF_TESTS_TO_RUN, so the appex-qa generator fans QA (ml_cpp_pr) and PyTorch suites out into concurrent parallel jobs in one downstream build (avoiding the skip_queued_branch_builds de-dup that dropped one of two separate triggers). run_qa_tests.yml.sh now derives its step label and commit status context (QA / PyTorch / QA + PyTorch) from the requested suites. Adds "import os" to pipeline.json.py: 8.19 did not previously import it and the consolidated block reads QAF_TESTS_TO_RUN via os.environ. Co-authored-by: Cursor <cursoragent@cursor.com>
edsavage
enabled auto-merge (squash)
July 31, 2026 03:03
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
1 participant
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.
Manual backport of #3131 to 8.19.
The auto-backport failed on merge conflicts: 8.19 lacks the "Upload ES inference tests x86_64" step that sits directly above the QA-trigger block on main, so the hunk context could not anchor. The resolution also needed an extra
import osin.buildkite/pipeline.json.py(8.19 did not previously import it, and the consolidated block readsQAF_TESTS_TO_RUNviaos.environ).No logic changes versus main. The consolidated single trigger emits a comma-separated
QAF_TESTS_TO_RUNso the appex-qa generator fans QA (ml_cpp_pr) and PyTorch suites out into concurrent parallel jobs, andrun_qa_tests.yml.shderives its step label / commit-status context (QA / PyTorch / QA + PyTorch) from the requested suites.Verified via dry-run on a fresh 8.19 checkout:
pipeline.json.pyruns and emits the correct single upload step +QAF_TESTS_TO_RUNfor QA-only (ml_cpp_pr), PyTorch-only (pytorch_tests) and combined (ml_cpp_pr,pytorch_tests) cases;run_qa_tests.yml.shpassesbash -nand emits valid YAML with the correct label/context per case.Made with Cursor