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

[ci][gh200] dockerfile clean up #11351

Merged
merged 27 commits into from
Dec 20, 2024
Merged

[ci][gh200] dockerfile clean up #11351

merged 27 commits into from
Dec 20, 2024

Conversation

youkaichao
Copy link
Member

built upon #11302 , check it out with another branch in the upstream repo so that we can test it before merging.

drikster80 and others added 23 commits November 20, 2024 21:37
…/causal-conv1d/mamba/flashinfer/bitsandbytes
# Conflicts:
#	docs/source/serving/deploying_with_docker.rst
…l && rm arm64 platform condition in requirements && add python3 use_existing_torch.py before build in run-gh200-test.sh
…& outlines == 0.1.11 # Requires pytorch && rm torch install before docker build
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
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 documentation Improvements or additions to documentation ci/build labels Dec 20, 2024
@youkaichao
Copy link
Member Author

thanks for the great work from @cennn

and also cc @drikster80 FYI , we decided to treat GH200 build a use case of "use existing torch", instead of hardcode the platform in requirements.txt .

@youkaichao
Copy link
Member Author

Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
@cennn
Copy link
Contributor

cennn commented Dec 20, 2024

look good to me!

Copy link
Contributor

@cennn cennn left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@cennn cennn left a comment

Choose a reason for hiding this comment

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

approved

@youkaichao youkaichao merged commit 7801f56 into main Dec 20, 2024
22 of 26 checks passed
@youkaichao youkaichao deleted the gh200_clean branch December 20, 2024 02:13
lucas-tucker pushed a commit to lucas-tucker/vllm-lucas-tucker that referenced this pull request Dec 21, 2024
Signed-off-by: drikster80 <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Co-authored-by: drikster80 <[email protected]>
Co-authored-by: cenzhiyao <[email protected]>
Signed-off-by: lucast2021 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants