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

[Train] Test if callbacks can be deepcopied #23496

Closed
wants to merge 1 commit into from

Conversation

Yard1
Copy link
Member

@Yard1 Yard1 commented Mar 25, 2022

Why are these changes needed?

Followup to #23333. Extends existing tests by checking if callbacks can be deepcopied.

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

Copy link
Contributor

@krfricke krfricke left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@amogkam amogkam left a comment

Choose a reason for hiding this comment

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

Wait @Yard1 dont we want to be testing tune callbacks as those are the ones that will be used with air? These train callbacks will eventually be deprecated.

in any case, I think ultimately we don’t want to be copying the run config at all, so deepcopy support for callbacks shouldn’t be necessary in the long run.

@Yard1
Copy link
Member Author

Yard1 commented Mar 25, 2022

@amogkam ok, will add tests for tune ones too!

@amogkam
Copy link
Contributor

amogkam commented Mar 25, 2022

@Yard1 I think we can close this in favor of #23499?

@amogkam
Copy link
Contributor

amogkam commented Mar 25, 2022

Like I don't think we should require callbacks to be deepcopyable...it will no longer be necessary after #23499, right?

@Yard1
Copy link
Member Author

Yard1 commented Mar 25, 2022

I mean, it doesn't hurt to test for it, but I guess it will become unnecessary. @krfricke what do you think?

@amogkam
Copy link
Contributor

amogkam commented Apr 4, 2022

@Yard1 should we close this?

@Yard1
Copy link
Member Author

Yard1 commented Apr 5, 2022

Yeah

@Yard1 Yard1 closed this Apr 5, 2022
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