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

[workflow] Enable setting workflow options on Ray DAGs #24210

Merged
merged 5 commits into from
Apr 27, 2022

Conversation

suquark
Copy link
Member

@suquark suquark commented Apr 26, 2022

Why are these changes needed?

This PR enables setting workflow options on Ray DAGs.

Related issue number

Checks

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

"name",
"metadata",
"catch_exceptions",
"max_retries",
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't max retries be unified?

Copy link
Member Author

Choose a reason for hiding this comment

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

I am not sure if it can be/should be unified. The max_retries in workflow retries at the python program layer and does not catch failures beyond normal exceptions. @iycheng

Copy link
Contributor

Choose a reason for hiding this comment

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

The semantics is different. I'd say either leave two APIs here or we give ray's max retries some default value.

@suquark suquark changed the title [WIP][workflow] Enable setting workflow options on Ray DAGs [workflow] Enable setting workflow options on Ray DAGs Apr 26, 2022
@fishbone
Copy link
Contributor

LGTM. I feel right now since we have already had to isolate workflow options with ray options, it's reasonable to put max_retries in workflow.

Copy link
Contributor

@fishbone fishbone left a comment

Choose a reason for hiding this comment

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

Let's wait for @ericl 's confirmation about the API.

Copy link
Contributor

@ericl ericl left a comment

Choose a reason for hiding this comment

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

I think we should revisit this later, but it's fine for current stage of workflows.

@ericl ericl added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Apr 26, 2022
@suquark
Copy link
Member Author

suquark commented Apr 27, 2022

The CI errors are not related. The MacOS errors are due to Exited with status -1 (agent lost). I'll merge it.

@suquark suquark merged commit 895fdb5 into ray-project:master Apr 27, 2022
@suquark suquark deleted the workflow_options branch April 27, 2022 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants