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][misc] allow to use recent numpy #12759

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

zhouyuan
Copy link
Contributor

@zhouyuan zhouyuan commented Feb 5, 2025

This patch removed the limitation on numpy < 2.0.0
outlines already did a workaround for running with recent numpy
dottxt-ai/outlines#1265

Fixes #6570

Copy link

github-actions bot commented Feb 5, 2025

👋 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 Feb 5, 2025
@jeejeelee jeejeelee requested a review from youkaichao February 5, 2025 03:38
@DarkLight1337
Copy link
Member

I think we also need to update the compiled requirements-test.txt?

try to remove limit on numpy version

Signed-off-by: Yuan Zhou <[email protected]>
@DarkLight1337
Copy link
Member

I think you need to pip compile with -P numpy to keep the numpy version in the output txt

@zhouyuan
Copy link
Contributor Author

zhouyuan commented Feb 5, 2025

I think you need to pip compile with -P numpy to keep the numpy version in the output txt

hi @DarkLight1337
it seems genai-perf has a requirement for old numpy, so pip compile will stick to 1.26.4
https://github.com/triton-inference-server/perf_analyzer/blob/main/genai-perf/pyproject.toml#L51
The genai-perf is only used in nightly benchmarks, but it's marked as one dependency in test. So I think we should try to bump the numpy in genai-perf package firstly?

-yuan

@DarkLight1337
Copy link
Member

cc @robertgshaw2-redhat

@mgoin
Copy link
Member

mgoin commented Feb 5, 2025

@debermudez @jikunshang could you help us understand if genai-perf can update to recent numpy?

@debermudez
Copy link

@mgoin this actually came up today in a different thread for our team. I think another team mate is already working on it.

@zhouyuan
Copy link
Contributor Author

zhouyuan commented Feb 5, 2025

Yes, here's the feedback from genai-perf dev
triton-inference-server/perf_analyzer#272 (comment)

@dyastremsky
Copy link

Done, thanks for raising this! triton-inference-server/perf_analyzer#275

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.

Upgrade to numpy >= 2.0.0
5 participants