Skip to content

[Test] Attempt all TPU V1 tests, even if some of them fail.#17334

Merged
robertgshaw2-redhat merged 6 commits intovllm-project:mainfrom
yarongmu-google:test
May 8, 2025
Merged

[Test] Attempt all TPU V1 tests, even if some of them fail.#17334
robertgshaw2-redhat merged 6 commits intovllm-project:mainfrom
yarongmu-google:test

Conversation

@yarongmu-google
Copy link
Contributor

@yarongmu-google yarongmu-google commented Apr 28, 2025

Currently if one test fails, all subsequent ones do not run.

Signed-off-by: Yarong Mu <ymu@google.com>
@github-actions
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

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 either: Add ready label to the PR or enable auto-merge.

🚀

@yarongmu-google
Copy link
Contributor Author

@mergify mergify bot added the ci/build label Apr 28, 2025
Copy link
Collaborator

@yaochengji yaochengji 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 enhancement!

@yaochengji yaochengji added tpu Related to Google TPUs ready ONLY add when PR is ready to merge/full CI is needed labels May 5, 2025
@mergify mergify bot removed the tpu Related to Google TPUs label May 5, 2025
@mergify
Copy link

mergify bot commented May 7, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @yarongmu-google.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label May 7, 2025
yarongmu-google and others added 2 commits May 8, 2025 15:50
Signed-off-by: Yarong Mu <ymu@google.com>
@mergify mergify bot removed the needs-rebase label May 8, 2025
Signed-off-by: Yarong Mu <ymu@google.com>
Signed-off-by: Yarong Mu <ymu@google.com>
@yarongmu-google
Copy link
Contributor Author

@khluu Please review. Thanks!

@robertgshaw2-redhat robertgshaw2-redhat enabled auto-merge (squash) May 8, 2025 16:13
Copy link
Collaborator

@NickLucche NickLucche left a comment

Choose a reason for hiding this comment

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

Very much needed!
On the other hand it would be nice to move all this logic at the buildkite level or any "steps" system that would help cleaning out the repetitive bits here.

@robertgshaw2-redhat robertgshaw2-redhat merged commit a83a0f9 into vllm-project:main May 8, 2025
31 checks passed
princepride pushed a commit to princepride/vllm that referenced this pull request May 10, 2025
…ject#17334)

Signed-off-by: Yarong Mu <ymu@google.com>
Signed-off-by: 汪志鹏 <wangzhipeng628@gmail.com>
RichardoMrMu pushed a commit to RichardoMrMu/vllm that referenced this pull request May 12, 2025
…ject#17334)

Signed-off-by: Yarong Mu <ymu@google.com>
Signed-off-by: Mu Huai <tianbowen.tbw@antgroup.com>
mawong-amd pushed a commit to ROCm/vllm that referenced this pull request May 14, 2025
zzzyq pushed a commit to zzzyq/vllm that referenced this pull request May 24, 2025
…ject#17334)

Signed-off-by: Yarong Mu <ymu@google.com>
Signed-off-by: Yuqi Zhang <yuqizhang@google.com>
@mergify
Copy link

mergify bot commented May 28, 2025

⚠️ The sha of the head commit of this PR conflicts with #18865. Mergify cannot evaluate rules on this PR. ⚠️

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.

4 participants