[NOT FOR MERGE] Debug doc build

[GregoryComer]

Need to SSH into the doc upload job.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 5 New Failures, 1 Unrelated Failure

As of commit c4040fc with merge base 4f3f329 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / macos / macos-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_llama3_2_1b
• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 4c9b610a5c3402881873ce786737f7c48074b2ebeca7569b10b2d76884f59792 /exec failed with exit code 3
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 1b8c55617e60d93e04f29edb4b531bc61d27824b5402f6c6efed0112935d140b /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-small, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t a04278a205cb3ef6bae0a446884ec5e9caacc9113d2d4ea215faa5619c5caf6c /exec failed with exit code 1
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, non-quantized) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest-buck / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

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.