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

Revert "Revert "[ci/release] Move all release tests to use Ray jobs instead of SDK commands"" #30969

Merged
merged 10 commits into from
Jan 5, 2023

Conversation

krfricke
Copy link
Contributor

@krfricke krfricke commented Dec 8, 2022

Reverts #30956

Kai Fricke added 5 commits December 8, 2022 14:22
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
@krfricke
Copy link
Contributor Author

krfricke commented Dec 9, 2022

@rkooo567
Copy link
Contributor

Are we confident this will work 100%? Why don't we migrate gradually? Like moving the wholes suites to job based executor first

Copy link
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

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

Request change until we resolve the comment ^.

@krfricke
Copy link
Contributor Author

Yeah this is moving gradually (we default to sdk_command).

It's currently not working for some tests, e.g. #31123 has to be resolved first

@krfricke
Copy link
Contributor Author

Just to be clear, the relevant line (which was different in the original PR) is this:

DEFAULT_RUN_TYPE = "sdk_command"

Copy link
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

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

sgtm. do you migrate ml tests first? Feel free to merge it when it passes!

Kai Fricke added 3 commits January 5, 2023 10:05
Signed-off-by: Kai Fricke <kai@anyscale.com>

# Conflicts:
#	release/ray_release/glue.py
#	release/release_tests.yaml
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
@krfricke
Copy link
Contributor Author

krfricke commented Jan 5, 2023

A recent run of release tests passed (all failures are also failing on master): https://buildkite.com/ray-project/release-tests-pr/builds/24762

The default is to stay with sdk runner, so I'll merge this PR and we can the migrate the other tests piece by piece.

@krfricke krfricke merged commit b628c82 into master Jan 5, 2023
@krfricke krfricke deleted the revert-30956-revert-30946-ci/release/ray-jobs branch January 5, 2023 15:38
AmeerHajAli pushed a commit that referenced this pull request Jan 12, 2023
…nstead of SDK commands"" (#30969)

This will move _some_ more release tests to use Ray jobs instead of the anyscale SDK command runner. The default remains to use the SDK runner. Subsequent tests will be migrated piece by piece.

Signed-off-by: Kai Fricke <kai@anyscale.com>
tamohannes pushed a commit to ju2ez/ray that referenced this pull request Jan 25, 2023
…nstead of SDK commands"" (ray-project#30969)

This will move _some_ more release tests to use Ray jobs instead of the anyscale SDK command runner. The default remains to use the SDK runner. Subsequent tests will be migrated piece by piece.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: tmynn <hovhannes.tamoyan@gmail.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.

3 participants