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

[ci/train] Add Ray Train storage refactor CI tests #38457

Merged
merged 4 commits into from
Aug 17, 2023

Conversation

krfricke
Copy link
Contributor

@krfricke krfricke commented Aug 15, 2023

Why are these changes needed?

This PR adds CI runners for the Ray Train and Tune tests with the new storage context path enabled.

Many tests are excluded at first. We will iteratively work on enabling them to avoid having to fix a bunch of issues in one giant PR.

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 :(

Kai Fricke added 2 commits August 15, 2023 14:06
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>

##### STORAGE REFACTOR

- label: ":steam_locomotive: Train tests and examples"
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we also need to add:

  • 📖 Doc tests and examples (excluding Ray AIR examples)
  • ✈️ AIR tests (ray/air)
  • ✈️ AIR/ML release smoke tests

GPU:

  • 📺 ✈️ AIR GPU tests (ray/air)
  • 📺 🚂 Train GPU tests

Doctest would also probably fail.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok sounds good - I'll first take a stab with the current selection but can update later/soon.

Copy link
Contributor

Choose a reason for hiding this comment

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

Got it, should we coordinate with a spreadsheet and shard the fixes?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, let's update the names of these Train / Train + Tune ones to also be prefixed by "New persistence mode:"

Signed-off-by: Kai Fricke <kai@anyscale.com>
@krfricke krfricke marked this pull request as ready for review August 16, 2023 19:07
Copy link
Contributor

@justinvyu justinvyu left a comment

Choose a reason for hiding this comment

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

Thanks!

@krfricke krfricke merged commit 8c4f4a8 into ray-project:master Aug 17, 2023
61 of 65 checks passed
@krfricke krfricke deleted the train/storage-ci branch August 17, 2023 16:50
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
This PR adds CI runners for the Ray Train and Tune tests with the new storage context path enabled.

Many tests are excluded at first. We will iteratively work on enabling them to avoid having to fix a bunch of issues in one giant PR.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
This PR adds CI runners for the Ray Train and Tune tests with the new storage context path enabled.

Many tests are excluded at first. We will iteratively work on enabling them to avoid having to fix a bunch of issues in one giant PR.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Victor <vctr.y.m@example.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants