Skip to content

Consolidate A100 CUDA CI jobs into shared batch runners#19922

Open
Gasoonjia wants to merge 1 commit into
mainfrom
batched-a100-ci
Open

Consolidate A100 CUDA CI jobs into shared batch runners#19922
Gasoonjia wants to merge 1 commit into
mainfrom
batched-a100-ci

Conversation

@Gasoonjia
Copy link
Copy Markdown
Contributor

Summary:
Collapse the four A100 runners (per-model export + e2e for the two A100-only models) into two shared single-runner batch jobs driven by a shared config file. Each model is processed independently with per-model pass/fail reporting; a job is green only if all its models pass, and one model's failure never blocks another.

  • Add .ci/scripts/cuda_a100_models.txt: shared source of truth for which models need an A100 runner (one line per model).
  • Add .ci/scripts/export_model_artifact_batch.sh: loops the config, delegates to export_model_artifact.sh per model under set +e, writes per-model _status files + logs, prints a summary section (stdout + GITHUB_STEP_SUMMARY), emits ::error:: annotations, exits non-zero if any model failed.
  • Add .ci/scripts/test_model_e2e_batch.sh: runs install_requirements.sh once, reads each model's export status (skips with surfaced error if export failed), delegates to test_model_e2e.sh per model, prints the same style of summary, exits non-zero unless every model fully passed.

Summary:
Collapse the four A100 runners (per-model export + e2e for the two
A100-only models) into two shared single-runner batch jobs driven by a
shared config file. Each model is processed independently with per-model
pass/fail reporting; a job is green only if all its models pass, and one
model's failure never blocks another.

- Add .ci/scripts/cuda_a100_models.txt: shared source of truth for which
  models need an A100 runner (one line per model).
- Add .ci/scripts/export_model_artifact_batch.sh: loops the config,
  delegates to export_model_artifact.sh per model under set +e, writes
  per-model _status files + logs, prints a summary section (stdout +
  GITHUB_STEP_SUMMARY), emits ::error:: annotations, exits non-zero if any
  model failed.
- Add .ci/scripts/test_model_e2e_batch.sh: runs install_requirements.sh
  once, reads each model's export status (skips with surfaced error if
  export failed), delegates to test_model_e2e.sh per model, prints the same
  style of summary, exits non-zero unless every model fully passed.
- test_model_e2e.sh: add backward-compatible SKIP_INSTALL_REQUIREMENTS
  guard so the batch can run runtime setup once.
- cuda.yml: remove the two SocialLocalMobile A100 models (and their exclude
  rows) from the per-cell export/e2e matrices and simplify those runners
  back to plain A10G; add new export-models-cuda-a100 and
  test-models-cuda-a100-e2e jobs on linux.aws.a100 (timeout 150). The e2e
  job uses if: always() so exported models are still tested on a partial
  export failure.

Test Plan:
- bash -n on all three scripts; cuda.yml has no editor diagnostics.
- Local smoke tests of both batch orchestrators with stubbed per-model
  scripts: confirmed loop continues past failures, correct _status files,
  summaries, ::error:: + step-summary output, SKIP_INSTALL_REQUIREMENTS
  propagation, export-failed->skipped path, and exit codes (0 all-pass,
  1 on any failure / empty / missing config).
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Jun 1, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19922

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 Cancelled Job, 3 Unclassified Failures

As of commit c38e2ba with merge base 4469d84 (image):

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

CANCELLED JOB - The following job was cancelled. Please retry:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 1, 2026
@linux-foundation-easycla
Copy link
Copy Markdown

CLA Missing ID

  • ❌ The email address for the commit (c38e2ba) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant