Skip to content

Conversation

kebe7jun
Copy link
Contributor

@kebe7jun kebe7jun commented Jul 22, 2025

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.

Purpose

Unify the way CPUs are built to reduce unnecessary maintenance costs.

Test Plan

See CI.

Test Result

https://github.com/vllm-project/vllm/actions/runs/16434542371/job/46442029158?pr=21343

(Optional) Documentation Update

@mergify mergify bot added documentation Improvements or additions to documentation ci/build labels Jul 22, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request unifies the Dockerfiles for ARM and x86 CPU builds. However, the current method of setting the LD_PRELOAD environment variable dynamically based on the architecture is unreliable. The review suggests using an entrypoint script to ensure the variable is correctly set at runtime.

Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

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 either: Add ready label to the PR or enable auto-merge.

🚀

@kebe7jun kebe7jun force-pushed the fix/unify-cpu-dockerfile branch 5 times, most recently from f685564 to 73dc19b Compare July 22, 2025 04:19
@kebe7jun kebe7jun marked this pull request as ready for review July 22, 2025 04:42
@kebe7jun kebe7jun requested a review from hmellor as a code owner July 22, 2025 04:42
Comment on lines 10 to 13
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest, ubuntu-24.04-arm]
Copy link
Member

Choose a reason for hiding this comment

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

This workflow is just for checking the Helm charts, is it necessary to run it on multiple hardwares?

Copy link
Contributor Author

@kebe7jun kebe7jun Jul 23, 2025

Choose a reason for hiding this comment

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

This test is not just a deployment test of helm, but actually tests the most basic reasoning ability. Or do you mean that we should build some real arm tests? Or do you mean that there is no need for arm tests?
We currently lack arm cpu tests, and it is a good idea to use Github's actions arm runner to do basic smoke testing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hmellor Any feedback? Should I remove it?

Copy link
Member

Choose a reason for hiding this comment

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

Perhaps you can run this only on Arm platform as a basic smoke testing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, I don't quite understand. Do you mean to keep only ubuntu-24.04-arm?

Copy link
Member

Choose a reason for hiding this comment

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

Right, to save the time :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, updated. BTW, these two are actually executed concurrently.

Copy link
Member

@bigPYJ1151 bigPYJ1151 left a comment

Choose a reason for hiding this comment

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

LGTM, just some nits. Please take a look.

Please also update the note on top of the Dockerfile.cpu and add note for build argument --platform.

Comment on lines 10 to 13
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest, ubuntu-24.04-arm]
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps you can run this only on Arm platform as a basic smoke testing.

@kebe7jun kebe7jun force-pushed the fix/unify-cpu-dockerfile branch 2 times, most recently from c27f79b to 51bf7c4 Compare July 25, 2025 09:21
@kebe7jun kebe7jun force-pushed the fix/unify-cpu-dockerfile branch from 51bf7c4 to 8728c90 Compare July 25, 2025 09:22
Copy link
Member

@bigPYJ1151 bigPYJ1151 left a comment

Choose a reason for hiding this comment

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

Thanks for the refactor :)

Hope @hmellor 's concern also is resolved. Let's see whether related tests can pass.

@bigPYJ1151 bigPYJ1151 added the ready ONLY add when PR is ready to merge/full CI is needed label Jul 25, 2025
@bigPYJ1151 bigPYJ1151 enabled auto-merge (squash) July 25, 2025 12:48
@simon-mo simon-mo disabled auto-merge July 25, 2025 14:33
@simon-mo simon-mo merged commit 396ee94 into vllm-project:main Jul 25, 2025
45 of 47 checks passed
@kebe7jun kebe7jun deleted the fix/unify-cpu-dockerfile branch July 25, 2025 14:35
@hmellor
Copy link
Member

hmellor commented Jul 25, 2025

Yeah my concern is resolved. I was just pointing out that that GitHub actions workflow is just for testing Helm charts work properly and that the images built in the workflow are not kept/uploaded anywhere, so it wasn't worth doing both.

@hmellor
Copy link
Member

hmellor commented Jul 30, 2025

Since switching to the arm GitHub actions runners, the lint-and-deploy workflow has been taking almost 3x longer and is causing long queues in our GitHub Actions jobs

@kebe7jun
Copy link
Contributor Author

Since switching to the arm GitHub actions runners, the lint-and-deploy workflow has been taking almost 3x longer and is causing long queues in our GitHub Actions jobs

Then I'll submit a PR to switch back. I didn't notice the time cost of this Pipeline before.

@hmellor
Copy link
Member

hmellor commented Jul 30, 2025

No problem, we weren't to know it'd be that much slower. Please cc me in your PR :)

wenscarl pushed a commit to wenscarl/vllm that referenced this pull request Aug 4, 2025
x22x22 pushed a commit to x22x22/vllm that referenced this pull request Aug 5, 2025
Pradyun92 pushed a commit to Pradyun92/vllm that referenced this pull request Aug 6, 2025
npanpaliya pushed a commit to odh-on-pz/vllm-upstream that referenced this pull request Aug 6, 2025
jinzhen-lin pushed a commit to jinzhen-lin/vllm that referenced this pull request Aug 9, 2025
paulpak58 pushed a commit to paulpak58/vllm that referenced this pull request Aug 13, 2025
taneem-ibrahim pushed a commit to taneem-ibrahim/vllm that referenced this pull request Aug 14, 2025
BoyuanFeng pushed a commit to BoyuanFeng/vllm that referenced this pull request Aug 14, 2025
diegocastanibm pushed a commit to diegocastanibm/vllm that referenced this pull request Aug 15, 2025
epwalsh pushed a commit to epwalsh/vllm that referenced this pull request Aug 28, 2025
googlercolin pushed a commit to googlercolin/vllm that referenced this pull request Aug 29, 2025
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 ready ONLY add when PR is ready to merge/full CI is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants