[CI/Build] Install uv for AMD MI300: Language Models Tests (Hybrid) %N

[amdfaa]

Purpose

This PR is for fixing the AMD MI300: Language Models Tests (Hybrid) %N failing with uv: command not found
See failing build:
https://buildkite.com/vllm/ci/builds/37631/steps/canvas?sid=019a5264-347a-407b-8a34-6d54a2f8e82f

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.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[gemini-code-assist]

Code Review

This pull request fixes a CI failure in the 'AMD MI300: Language Models Tests' job by installing uv before it is used. The change is correct and directly addresses the uv: command not found error. I have one suggestion to pin the version of uv to ensure build reproducibility and prevent potential breakages from future uv releases. This is a standard practice for maintaining stable CI environments.

[gemini-code-assist]

For better reproducibility and to prevent unexpected build failures due to updates in uv, it's recommended to pin the version of uv being installed. This ensures that the CI environment remains stable and predictable over time. Please pin it to a recent, stable version that is known to work.

    - pip install uv==0.2.21

[zhewenl]

let's fix it in test-amd.yaml? also I think install UV in docker image should be more appropriate.

cc @Alexei-V-Ivanov-AMD @gshtras

[amdfaa]

let's fix it in test-amd.yaml? also I think install UV in docker image should be more appropriate.

cc @Alexei-V-Ivanov-AMD @gshtras

That makes sense. I'll add it to the requirements file and remove the current changes. @zhewenl

[zhewenl]

That makes sense. I'll add it to the requirements file and remove the current changes. @zhewenl

I am not sure if adding to deps list is sufficient - maybe trigger a test on AMD CI to test if uv issue is gone?
Here is how Nvidia setting up UV in docker: https://github.com/vllm-project/vllm/blob/main/docker/Dockerfile#L90-L91, and I had a draft PR for an example: #27716

[amdfaa]

That makes sense. I'll add it to the requirements file and remove the current changes. @zhewenl

I am not sure if adding to deps list is sufficient - maybe trigger a test on AMD CI to test if uv issue is gone? Here is how Nvidia setting up UV in docker: https://github.com/vllm-project/vllm/blob/main/docker/Dockerfile#L90-L91, and I had a draft PR for an example: #27716

This is a recent run based on my commit to add package to the dependencies. It looks like it worked. Can you confirm this and merge if you think it's good @zhewenl ?

https://buildkite.com/vllm/ci/builds/37752/steps/canvas?sid=019a55dd-7925-4543-bff0-be282fbbbec0

[zhewenl]

@amdfaa I think you need to trigger a test in AMD CI, the test you linked is running on Nvidia. Example: #28156

cc @Alexei-V-Ivanov-AMD

[gshtras]

A bit late, but rather than changing the build process for the production image in order to fix the tests, potentially locking the run scenarios to the root user, isn't it better to address the test issue in the test?