Skip to content

[Bugfix] Avoid src/dst as None in irecv/isend_tensor_dict#35754

Merged
vllm-bot merged 5 commits intovllm-project:mainfrom
bigPYJ1151:fix_pp
Mar 3, 2026
Merged

[Bugfix] Avoid src/dst as None in irecv/isend_tensor_dict#35754
vllm-bot merged 5 commits intovllm-project:mainfrom
bigPYJ1151:fix_pp

Conversation

@bigPYJ1151
Copy link
Copy Markdown
Member

@bigPYJ1151 bigPYJ1151 commented Mar 2, 2026

Purpose

Test Plan

CI tests

Test Result


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.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

Signed-off-by: jiang1.li <jiang1.li@intel.com>
Signed-off-by: jiang1.li <jiang1.li@intel.com>
@mergify mergify Bot added ci/build cpu Related to CPU backends bug Something isn't working labels Mar 2, 2026
Copy link
Copy Markdown
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 fixes a bug where src and dst could be None when using the custom CPU communication path by moving the default value assignment to an earlier point in the functions. It also improves the CPU smoke test script to check for failed requests, making the CI more robust. My review identifies a potential race condition in the test script that could lead to flaky tests. The core bug fix in the Python code appears correct and well-implemented.

Comment thread .buildkite/scripts/hardware_ci/run-cpu-distributed-smoke-test.sh Outdated
Signed-off-by: jiang1.li <jiang1.li@intel.com>
@bigPYJ1151 bigPYJ1151 added the ready ONLY add when PR is ready to merge/full CI is needed label Mar 2, 2026
Signed-off-by: jiang1.li <jiang1.li@intel.com>
@bigPYJ1151 bigPYJ1151 removed the ready ONLY add when PR is ready to merge/full CI is needed label Mar 2, 2026
@bigPYJ1151
Copy link
Copy Markdown
Member Author

Hi @yewentao256 Could you please help to check this PR? Thank you :)

@bigPYJ1151 bigPYJ1151 requested a review from yewentao256 March 2, 2026 15:42
Copy link
Copy Markdown
Member

@yewentao256 yewentao256 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the work!

@@ -1,26 +1,43 @@
#!/bin/bash
set -euox pipefail
export VLLM_CPU_CI_ENV=0
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why do we need this?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It's to enable torch.compile for this test

@yewentao256 yewentao256 added the ready ONLY add when PR is ready to merge/full CI is needed label Mar 2, 2026
@bigPYJ1151 bigPYJ1151 enabled auto-merge (squash) March 3, 2026 13:02
@vllm-bot vllm-bot merged commit 440f0e7 into vllm-project:main Mar 3, 2026
53 of 55 checks passed
@bigPYJ1151 bigPYJ1151 added this to the v0.17.0 cherry picks milestone Mar 4, 2026
Copilot AI pushed a commit to machov/vllm that referenced this pull request Mar 10, 2026
avinashsingh77 pushed a commit to avinashsingh77/vllm that referenced this pull request Mar 12, 2026
wendyliu235 pushed a commit to wendyliu235/vllm-public that referenced this pull request Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ci/build cpu Related to CPU backends 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.

3 participants