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

[Hardware][Gaudi][Bugfix] Fix set_forward_context arguments and CI test execution #12014

Merged

Conversation

kzawora-intel
Copy link
Contributor

@kzawora-intel kzawora-intel commented Jan 13, 2025

This PR fixes HPU crashes introduced in #11967, occuring due to set_forward_context being set too early, with attn_metadata not containing all the required fields. Additionally, it fixes the bug in CI HPU scripts, where test return code was not taken into account, and it always succeeded. I've also updated Dockerfile.hpu to use latest SynapseAI 1.19.1 build with PT 2.5.1, as 1.18.0 release had a bug which may result in overriding test exit code separately.

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 13, 2025
@kzawora-intel kzawora-intel force-pushed the private/kzawora/set_forward_context branch from 5403538 to 0f60e48 Compare January 13, 2025 17:48
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.

thanks for the fix!

@youkaichao youkaichao enabled auto-merge (squash) January 14, 2025 02:59
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Jan 14, 2025
@youkaichao
Copy link
Member

the test is green now, merging.

@youkaichao youkaichao disabled auto-merge January 14, 2025 03:04
@youkaichao youkaichao merged commit 078da31 into vllm-project:main Jan 14, 2025
31 of 81 checks passed
ice-tong pushed a commit to ice-tong/vllm that referenced this pull request Jan 18, 2025
joennlae pushed a commit to 44ai-labs/vllm that referenced this pull request Jan 19, 2025
joennlae pushed a commit to 44ai-labs/vllm that referenced this pull request Jan 19, 2025
HwwwwwwwH pushed a commit to HwwwwwwwH/vllm that referenced this pull request Jan 22, 2025
abmfy pushed a commit to abmfy/vllm-flashinfer that referenced this pull request Jan 24, 2025
abmfy pushed a commit to abmfy/vllm-flashinfer that referenced this pull request Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build 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.

2 participants