[ROCm] Migrate xgrammar to upstream release

[AndreasKaratzas]

This PR updates the xgrammar dependency in requirements/rocm-test.txt from a custom fork to the upstream PyPI release.

Changes

• Replaced xgrammar @ git+https://github.com/divakar-amd/xgrammar@3272f7c... with xgrammar==0.1.29

Motivation

It's better practice to use upstream repositories instead of maintaining custom forks when possible. This is a follow-up to a comment from #29702 to eventually migrate to the upstream xgrammar repo.

Testing

Verified on ROCm with the following tests passing:

pytest -v -s tests/v1/e2e/test_async_scheduling.py
pytest -v -s tests/v1/entrypoints/llm/test_struct_output_generate.py::test_structured_output_auto_mode[Qwen/Qwen2.5-1.5B-Instruct-auto]
pytest -v -s tests/v1/e2e/test_spec_decode.py

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.

[gemini-code-assist]

Code Review

This pull request updates the xgrammar dependency in requirements/rocm-test.txt from a forked repository to the official PyPI release xgrammar==0.1.29. This is a beneficial change, as it aligns with best practices by using an upstream release over a custom fork, which improves maintainability. The change is straightforward, and the author has confirmed that relevant tests pass on ROCm, mitigating the primary risk associated with such a migration. The PR is well-motivated and appears correct.

[AndreasKaratzas]

Update: Bumped xgrammar to 0.1.29 in common.txt.

This resolves a dependency conflict with rocm-test.txt which required 0.1.29, while common.txt pinned 0.1.27. Since rocm-test.txt includes common.txt via -r common.txt, uv couldn't resolve both constraints simultaneously.

The reason we need 0.1.29 for ROCm: it includes a fix for the Triton kernel warp size on AMD GPUs (mlc-ai/xgrammar#476). Without this fix, structured output on MI300 fails with:

triton.runtime.errors.OutOfResources: out of resource: threads, Required: 2048, Hardware limit: 1024

The issue was that the Triton kernel hardcoded warp size to 64 (NVIDIA), but AMD GPUs use warp size 32. This caused the kernel to request more threads than available on AMD hardware.

[AndreasKaratzas]

There is an AMD CI run for this PR before and after this addition, and it looks like everything is still the same:
Before: https://buildkite.com/vllm/amd-ci/builds/2103
After: https://buildkite.com/vllm/amd-ci/builds/2130

[LucasWilkinson]

cc @tjtanaa

[DarkLight1337]

Renamed the PR and triggered all tests as it also affects the default vLLM installation via common.txt.

[AndreasKaratzas]

@DarkLight1337 These b200 failures are not xgrammar related and are already known right? I have few of them already here: #30719