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

[tune] Fix new output path with new execution path [no_early_kickoff] #33880

Merged
merged 1 commit into from
Mar 29, 2023

Conversation

krfricke
Copy link
Contributor

Why are these changes needed?

The new experimental output path (#33609) and the new experimental execution engine (#33499) currently don't work together because the new output path is calling a trial executor API directly (which does not exist in the experimental execution engine).

This PR calls the correct API on the TrialRunner/TuneController so both features can be tested together.

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

Copy link
Contributor

@xwjiang2010 xwjiang2010 left a comment

Choose a reason for hiding this comment

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

ah thanks! didn't realize that this branch did not get updated.

Copy link
Collaborator

@zhe-thoughts zhe-thoughts left a comment

Choose a reason for hiding this comment

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

Approved for merging to master

@krfricke krfricke merged commit b9a8ee9 into ray-project:master Mar 29, 2023
@krfricke krfricke deleted the tune/new-output-execution branch March 29, 2023 22:07
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
…ray-project#33880)

The new experimental output path (ray-project#33609) and the new experimental execution engine (ray-project#33499) currently don't work together because the new output path is calling a trial executor API directly (which does not exist in the experimental execution engine).

This PR calls the correct API on the TrialRunner/TuneController so both features can be tested together.

Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: elliottower <[email protected]>
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
…ray-project#33880)

The new experimental output path (ray-project#33609) and the new experimental execution engine (ray-project#33499) currently don't work together because the new output path is calling a trial executor API directly (which does not exist in the experimental execution engine).

This PR calls the correct API on the TrialRunner/TuneController so both features can be tested together.

Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Jack He <[email protected]>
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