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.

Sign up for GitHub

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

Jump to bottom

[tune] filter placement group resources if not in use #16996

Merged
merged 3 commits into from
Jul 16, 2021
Merged

[tune] filter placement group resources if not in use #16996

merged 3 commits into from
Jul 16, 2021

Conversation

krfricke
Copy link
Contributor

Why are these changes needed?

cc @Tonyhao96

Related issue number

Closes #16874

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

@krfricke krfricke added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Jul 14, 2021
@richardliaw richardliaw merged commit 49b72ee into ray-project:master Jul 16, 2021
@krfricke krfricke deleted the filter-resources branch September 22, 2023 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@richardliaw richardliaw richardliaw approved these changes

Assignees

@richardliaw richardliaw

Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Tune] Progress report becomes strange after upgrading to ray 1.4.1
2 participants
@krfricke @richardliaw