Skip to content

Conversation

@killershrimp
Copy link
Contributor

@killershrimp killershrimp commented Aug 28, 2025

cc @njhill

Purpose

Reduce CI time by deferring multi-gpu weightloading tests to nightly. First part of #23669

Test Plan

n/a


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

Signed-off-by: Alex Yun <alexyun04@gmail.com>
@mergify mergify bot added the ci/build label Aug 28, 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 aims to move multi-GPU weight loading tests to a nightly schedule to reduce CI time. The current change marks the test step as optional in the Buildkite pipeline. However, this only disables the test from running on pull requests and does not configure it to run nightly. This creates a temporary but significant gap in test coverage until the nightly schedule is implemented. I have raised a high-severity concern about this and recommended including the nightly schedule configuration in this same PR to avoid introducing regressions.

mirror_hardwares: [amdexperimental]
working_dir: "/vllm-workspace/tests"
num_gpus: 2
optional: true
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This change makes the 'Test Multi-GPU Weight Loading (AMD)' step optional, effectively disabling it from running on pull requests. While the goal is to move this to a nightly run, this pull request only implements the first part of that change.

Merging this PR as-is will create a gap in test coverage, as these multi-GPU tests will not run at all until the nightly schedule is configured to un-block this step. This could allow regressions to be introduced undetected.

It would be safer to include the changes for the nightly schedule in this same pull request to avoid any period where these important tests are disabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

my understanding is that all optional tests will be run automatically every night, so nothing else needs to be changed (#10465)

@DarkLight1337 DarkLight1337 enabled auto-merge (squash) August 28, 2025 04:25
@DarkLight1337 DarkLight1337 added the ready ONLY add when PR is ready to merge/full CI is needed label Aug 28, 2025
@vllm-bot vllm-bot merged commit f48a9af into vllm-project:main Aug 28, 2025
19 of 66 checks passed
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Aug 28, 2025
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Sep 3, 2025
eicherseiji pushed a commit to eicherseiji/vllm that referenced this pull request Sep 9, 2025
FeiDaLI pushed a commit to FeiDaLI/vllm that referenced this pull request Sep 25, 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.

3 participants