[WIP][XPU] upgrade torch-xpu to 2.12

[jikunshang]

Purpose

Test Plan

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[mergify]

Documentation preview: https://vllm--42262.org.readthedocs.build/en/42262/

[gemini-code-assist]

Code Review

This pull request updates XPU-related dependencies, bumping torch to 2.12.0+xpu and triton-xpu to 3.7.1, while also modifying the pre-commit configuration to exclude various torch and NVIDIA/CUDA packages from generated requirement files. Feedback highlights that the XPU installation documentation was mistakenly emptied and should be updated with the new version requirements. Additionally, there are concerns regarding the use of a test index URL and the lack of version pinning for torchaudio and torchvision, which may lead to environment instability.

I am having trouble creating individual review comments. Click here to see my feedback.

docs/getting_started/installation/gpu.xpu.inc.md (1-98)

The XPU installation guide content has been completely removed. This file should be updated to reflect the new version requirements (e.g., Torch 2.12 and Triton-XPU 3.7.1) rather than being emptied, as it is essential for users setting up the XPU backend.

requirements/xpu.txt (13-16)

The use of the test/xpu index and the lack of version pinning for torchaudio and torchvision introduce potential instability. Since torch is pinned to 2.12.0+xpu, torchaudio and torchvision should also be pinned to their matching XPU versions to ensure a consistent and reproducible environment. Furthermore, the index should be switched back to the stable one once the upgrade is finalized.

[mergify]

Documentation preview: https://vllm--42262.org.readthedocs.build/en/42262/

[hmellor]

Instead of duplicating this block please use yaml anchors like we do for mypy

vllm/.pre-commit-config.yaml

Lines 151 to 163 in 4200f62

	- id: mypy-3.10 # TODO: Use https://github.com/pre-commit/mirrors-mypy when mypy setup is less awkward
	name: Run mypy for Python 3.10
	entry: python tools/pre_commit/mypy.py "3.10"
	<<: &mypy_common
	language: python
	types_or: [python, pyi]
	require_serial: true
	additional_dependencies: ["mypy==1.20.2", regex, types-cachetools, types-setuptools, types-PyYAML, types-requests, types-torch, pydantic]
	- id: mypy-3.11 # TODO: Use https://github.com/pre-commit/mirrors-mypy when mypy setup is less awkward
	name: Run mypy for Python 3.11
	entry: python tools/pre_commit/mypy.py "3.11"
	<<: *mypy_common
	stages: [manual] # Only run in CI

[hmellor]

Another question would be, why have we stopped using --torch-backend?

[jikunshang]

I will revert it back. I tried before torch 2.12 release, with torch test channel(https://download.pytorch.org/whl/test/xpu), which will throw some compatible issue, so I follow what rocm did. I think it will no longer be a issue since torch 2.12 is released. thanks for your review!

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @jikunshang.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @jikunshang.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork