Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Build] update requirements of no-device for plugin usage #12630

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

sducouedic
Copy link
Contributor

@sducouedic sducouedic commented Jan 31, 2025

For a lot of backend devices, the requirements consists of requirements-common.txt + some other python packages. Therefore, when installing a plugin we first want to install vllm with requirements-common.txt in a first step, and then install requirements-{plugin}.txt through the plugin.

When doing this, VLLM_TARGET_DEVICE cannot be directly set as the name of the target device (e.g. "spyre" would raise an "Unknown runtime environment" error), therefore setting VLLM_TARGET_DEVICE as empty is the best solution so far, but it downloads some unnecessary packages unrelated to the target device.

Note: another possibility could be to add "oot" as additional accepted value for VLLM_TARGET_DEVICE, which would install requirements-common.txt only.

@MengqingCao tagging you because you are the last one that modified that line.
cc @youkaichao

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
Copy link

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@mergify mergify bot added the ci/build label Jan 31, 2025
Copy link
Member

@youkaichao youkaichao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@youkaichao youkaichao merged commit 649550f into vllm-project:main Feb 4, 2025
18 of 21 checks passed
fxmarty-amd pushed a commit to fxmarty-amd/vllm that referenced this pull request Feb 7, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
Signed-off-by: Felix Marty <felmarty@amd.com>
ShangmingCai pushed a commit to ShangmingCai/vllm that referenced this pull request Feb 10, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
panf2333 pushed a commit to yottalabsai/vllm that referenced this pull request Feb 18, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
@sducouedic sducouedic deleted the plugin_use_no_device branch February 19, 2025 16:03
kerthcet pushed a commit to kerthcet/vllm that referenced this pull request Feb 21, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
lk-chen pushed a commit to lk-chen/vllm that referenced this pull request Mar 5, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
Signed-off-by: Linkun Chen <github@lkchen.net>
Said-Akbar pushed a commit to Said-Akbar/vllm-rocm that referenced this pull request Mar 7, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
Signed-off-by: saeediy <saidakbarp@gmail.com>
qscqesze pushed a commit to ZZBoom/vllm that referenced this pull request Mar 13, 2025
…ct#12630)

Signed-off-by: Sophie du Couédic <sop@zurich.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants