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

[Core][Nightly test] use smaller instance for scheduling tests #25635

Merged
merged 1 commit into from
Jun 10, 2022

Conversation

mwtian
Copy link
Member

@mwtian mwtian commented Jun 9, 2022

Why are these changes needed?

m5.16xlarge instances have 64 CPU and 256GB memory, which are overkill for scheduling tests that do not have a lot of computations. Use smaller instance m5.4xlarge to save cost and make allocating instances easier.

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

@mwtian
Copy link
Member Author

mwtian commented Jun 10, 2022

Verified that the existing failures of scheduling_test_many_0s_tasks_many_nodes still happen on the new configuration.
Screen Shot 2022-06-09 at 8 10 53 PM

@mwtian mwtian added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants