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

[core] Block before running gpu tests #51131

Merged
merged 4 commits into from
Mar 7, 2025

Conversation

dayshah
Copy link
Contributor

@dayshah dayshah commented Mar 6, 2025

Why are these changes needed?

A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@dayshah dayshah added the go add ONLY when ready to merge, run all tests label Mar 6, 2025
Comment on lines +402 to +403
- block: "run multi gpu tests"
if: build.env("BUILDKITE_PIPELINE_ID") == "0189942e-0876-4b8f-80a4-617f988ec59b" || build.env("BUILDKITE_PIPELINE_ID") == "018f4f1e-1b73-4906-9802-92422e3badaa"
Copy link
Collaborator

Choose a reason for hiding this comment

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

please give it a key and add depends_on in the multi gpu tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added

dayshah added 2 commits March 6, 2025 10:20
Signed-off-by: dayshah <[email protected]>
@dayshah dayshah requested a review from aslonnie March 6, 2025 18:49
Copy link
Contributor

@ruisearch42 ruisearch42 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 PR

@@ -409,4 +416,4 @@ steps:
--build-name coregpubuild
--only-tags multi_gpu
--install-mask serve
depends_on: coregpubuild
Copy link
Contributor

Choose a reason for hiding this comment

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

QQ: should coregpubuild be kept?

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes.

Copy link
Collaborator

Choose a reason for hiding this comment

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

make depends_on a list

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so i'm actually unsure if we should keep that because it's not always reliable, ex. when I change the actual tests it doesn't always actually run these tests. I think it makes more sense to just keep it fully up to the user.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm good w/ making it fully manual (like win & mac tests)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

talked to lonnie -> still need depends on coregpubuild because it still depends on like the actual build

@aslonnie aslonnie merged commit 47f930f into ray-project:master Mar 7, 2025
5 checks passed
@dayshah dayshah deleted the block-gpu-tests branch March 7, 2025 17:29
elimelt pushed a commit to elimelt/ray that referenced this pull request Mar 9, 2025
A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

---------

Signed-off-by: dayshah <[email protected]>
park12sj pushed a commit to park12sj/ray that referenced this pull request Mar 18, 2025
A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

---------

Signed-off-by: dayshah <[email protected]>
jaychia pushed a commit to jaychia/ray that referenced this pull request Mar 19, 2025
A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

---------

Signed-off-by: dayshah <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
jaychia pushed a commit to jaychia/ray that referenced this pull request Mar 19, 2025
A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

---------

Signed-off-by: dayshah <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Drice1999 pushed a commit to Drice1999/ray that referenced this pull request Mar 23, 2025
A lot of things change coregpubuild so the multi gpu tests run more often than they need to. We're moving to manually running these multi-gpu tests.

---------

Signed-off-by: dayshah <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants