ci(pytorch): derive numpy test pin from vendored torch checkout

[lucbruni-amd]

Motivation

Follow-up / alternative to the review discussion on #6400. The unpinned numpy
in external-builds/pytorch/requirements-test.txt broke the non-full PyTorch
test workflow once a newer NumPy tightened uint8 casting (an upstream OpInfo
bug, pytorch/pytorch#189267). #6400 fixes it by hand-copying upstream's
per-Python numpy pins, but there is silent drift potential.

This prototype removes the manual copy: it derives numpy from the checked-out
torch's own .ci/docker/requirements-ci.txt at install time, so we always use
what upstream validates for the exact ref under test.

Note: the full test workflow already installs the entire requirements-ci.txt
(since #3705), so it is already covered; this only closes the gap in the lean
non-full test_pytorch_wheels.yml without pulling upstream's ~75-package set.

Technical Details

• external-builds/pytorch/derive_test_requirements.py: prints the requirement
  lines for the requested packages (default numpy) from the vendored checkout's
  .ci/docker/requirements-ci.txt, preserving environment markers; errors if the
  file is missing.
• requirements-test.txt: drop bare numpy (now derived).
• test_pytorch_wheels.yml: after installing the lean reqs, pipe the derived
  pins into pip.

It auto-tracks the torch ref (nightly → nightly's numpy, release/2.9 → 2.9's
numpy), so there is nothing to re-sync and nothing to drop when
pytorch/pytorch#189267 is fixed upstream.

Test Plan

Local verification (below); in CI, the non-full PyTorch test jobs install the
derived numpy and the threshold uint8 tests pass.

Test Result

Ran locally against the vendored checkout:

• default → nightly's 4 per-Python numpy lines
• marker selection for py3.12 → numpy==1.26.2
• --requirements-ci pointed at ROCm/pytorch release/2.9 → numpy==2.0.2 / 2.1.2 (per-branch tracking)
• missing file → clean error (exit 2)

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[therock-pr-bot]

✅ All Checks Passed — Ready for Review

Check	Status	Details
🌿 Branch Name	✅ Pass	—
📝 PR Title/Description	✅ Pass	—
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	—
🔎 pre-commit	✅ Pass	—
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—
🤖 therock-pr-bot	✅ Pass	—

🎉 All checks passed! This PR is ready for review.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

[therock-pr-bot]

Pre-commit check failed

⛔ pre-commit failed

Please run locally:

• python -m pip install pre-commit
• pre-commit install
• pre-commit run --all-files --show-diff-on-failure

This repo uses .pre-commit-config.yaml.

[therock-pr-bot]

🎉 All checks passed! This PR is ready for review.

[Copilot]

Pull request overview

This PR updates the lean (non-full) PyTorch wheel test workflow to avoid manual NumPy pin drift by deriving the NumPy requirement directly from the checked-out PyTorch source tree’s .ci/docker/requirements-ci.txt, matching what upstream validates for the exact ref under test.

Changes:

• Remove the bare numpy entry from external-builds/pytorch/requirements-test.txt and document that NumPy is derived at test time.
• Add external-builds/pytorch/derive_test_requirements.py to extract and print requirement lines (default: numpy) from the vendored PyTorch checkout’s CI requirements file.
• Update .github/workflows/test_pytorch_wheels.yml to install the derived NumPy pins after installing the lean test requirements.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
external-builds/pytorch/requirements-test.txt	Drops bare numpy and documents that NumPy is now derived per torch ref.
external-builds/pytorch/derive_test_requirements.py	Adds a helper to extract pinned requirement lines (e.g., NumPy) from the checked-out PyTorch repo’s CI requirements file.
.github/workflows/test_pytorch_wheels.yml	Installs derived NumPy pins in the non-full wheel test workflow to avoid upstream drift.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[lucbruni-amd]

Possibly superseded by #6384.