optimum pin bump

[JacobSzwejbka]

Bring in the cuda-windows recipe

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 4 Cancelled Jobs, 5 Unrelated Failures

As of commit 6a06d9d with merge base f9953b6 ():

NEW FAILURE - The following job has failed:

• pull / test-lora-linux / linux-job (gh)
  RuntimeError: Command docker exec -t a9af5820fc2b17e721c834813d4900fb53d1e9243ecca961873786091889cdcf /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• Lint / link-check / lint-file-size / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-multimodal-linux (gemma3-4b) / linux-job (gh)
  ##[error]The operation was canceled.
• pull / unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (gh)
  ##[error]The operation was canceled.
• pull / unittest-editable / linux / linux-job (gh)
  ##[error]The operation was canceled.

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• docker-builds / docker-build (linux.4xlarge, executorch-ubuntu-22.04-gcc9) (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following jobs failed but was present on the merge base:

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

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-openvino-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)

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.

[meta-codesync]

@JacobSzwejbka has imported this pull request. If you are a Meta employee, you can view this in D88787322.