Move Linux CI jobs from linux_job_v2 to linux_job_v3 (OSDC)

[huydhn]

Part 2 of moving ExecuTorch's Linux CI to OSDC. Independent of #22106; #22108 stacks on this.

87 call sites across 24 workflows move to linux_job_v3. ROCm stays on v2 — no OSDC hardware.

Most of the diff is mechanical. The part worth review is the CI image: v3 hands docker-image straight to the pod's container:, which the kubelet pulls before any step runs, so v2's in-job calculate-docker-image — which both resolved ci-image:<name> and waited for docker-builds to push it — has nowhere left to run. _docker-image.yml replaces both halves, and callers name the image in full. Reusable workflows keep taking ci-image:<name> unchanged, so their own callers did not move.

doc-build's upload-gh-pages no longer needs run-with-docker: false, since v3 checks out and runs the script in one container.

Review order: _docker-image.yml, then _unittest.yml as a worked caller example, then the rest.

Draft until a CI run shows what OSDC's PyPI reachability breaks — cuda.yml already needed PIP_EXTRA_INDEX_URL cleared.

Authored with Claude Code.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 7 New Failures, 15 Pending, 5 Unclassified Failures

As of commit 61eba98 with merge base 9a2d135 ():

NEW FAILURES - The following jobs have failed:

• periodic / test-models-linux (buck2, mv3, portable, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• Test Vulkan Backend (specialized runners) / test-vulkan-nvidia / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1

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:

• cuda-perf / benchmark-cuda (nvidia/parakeet-tdt, non-quantized, nvidia_parakeet-tdt, 50) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 134
• cuda-perf / benchmark-cuda (nvidia/parakeet-tdt, quantized-int4-tile-packed, nvidia_parakeet-tdt, 50) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 134
• cuda-perf / benchmark-cuda (nvidia/parakeet-tdt, quantized-int4-weight-only, nvidia_parakeet-tdt, 50) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 134
• Test CUDA Builds / test-model-cuda-e2e-Qwen3.5-35B-A3B-HQQ-INT4-quantized-int4-tile-packed / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• Test CUDA Builds / unittest-cuda / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  test_device_planned_method_allocates_on_the_device

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

[github-actions]

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.

[huydhn]

Two follow-ups pushed:

• _docker-image.yml now fails fast (after a 5 minute grace period) when a commit changes .ci/docker but no docker-builds run exists for its SHA, telling you to apply the ciflow/docker label. Needed because Move docker-builds to OSDC runners #22106 drops docker-builds' pull_request trigger — without this the poll would sit for four hours before timing out.
• Blocked, like Move docker-builds to OSDC runners #22106, on meta-pytorch/pytorch-gha-infra#1443 for role/arc trust policy access.