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

Updating vLLM tests to handle changes between vLLM version 0.2.3 and 0.3.0 #30

Merged
merged 9 commits into from
Feb 7, 2024

Conversation

oandreeva-nv
Copy link
Contributor

Updated accuracy test not to run 2 vLLM engines at the same time, due to vllm-project/vllm#2248

@oandreeva-nv oandreeva-nv changed the title Oandreeva vllm upgrade 0.3.0 Updating vLLM accuracy test Feb 1, 2024
jbkyang-nvi
jbkyang-nvi previously approved these changes Feb 2, 2024
Copy link

@jbkyang-nvi jbkyang-nvi left a comment

Choose a reason for hiding this comment

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

lgtm!

jbkyang-nvi
jbkyang-nvi previously approved these changes Feb 2, 2024
@oandreeva-nv oandreeva-nv changed the title Updating vLLM accuracy test Updating vLLM tests to handle changes between vLLM version 0.2.3 and 0.3.0 Feb 7, 2024
Copy link

@jbkyang-nvi jbkyang-nvi 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 fixes!

with open("vllm_engine_output.pkl", "wb") as f:
pickle.dump(python_vllm_output, f)

return
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps the return statement can be removed here since it always returns None.

@oandreeva-nv oandreeva-nv merged commit 65821ed into main Feb 7, 2024
3 checks passed
@oandreeva-nv oandreeva-nv deleted the oandreeva_vllm_upgrade_0.3.0 branch February 7, 2024 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants