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

[RLlib] break up the learner group tests into shorter tests #35926

Merged

Conversation

avnishn
Copy link
Member

@avnishn avnishn commented May 31, 2023

break them up into 3 classes because they all take a very long time to run
causing timeouts on master

Signed-off-by: Avnish [email protected]

Why are these changes needed?

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

break them up into 3 classes  because they all take a very long time to run
causing timeouts on master

Signed-off-by: Avnish <[email protected]>
@avnishn
Copy link
Member Author

avnishn commented May 31, 2023

addressed comments

@@ -128,7 +128,7 @@ def test_learner_group_local(self):

def test_update_multigpu(self):
fws = ["torch", "tf2"]
scaling_modes = REMOTE_SCALING_CONFIGS.keys()
scaling_modes = ["multi-gpu-ddp", "remote-gpu"]
Copy link
Contributor

Choose a reason for hiding this comment

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

@avnishn Can you add explanations on why these changes are made? REMOTE_SCALING_CONFIGS.keys() --> ["multi-gpu-ddp", "remote-gpu"]?

Copy link
Member Author

Choose a reason for hiding this comment

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

We can reduce the number of tests that we need to run while getting full test coverage by doing this.

@@ -27,7 +27,7 @@
# --jobs 2 is necessary as we only need to have at least 2 gpus on the machine
Copy link
Contributor

Choose a reason for hiding this comment

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

comment still says --jobs 2 is necessary

Copy link
Member Author

Choose a reason for hiding this comment

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

yep I was exploring here. by removing jobs=2

I'm trying to understand where my cuda oom comes from

Copy link
Member Author

Choose a reason for hiding this comment

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

added this backl

@kouroshHakha kouroshHakha merged commit e6b5b8b into ray-project:master Jun 1, 2023
2 checks passed
scv119 pushed a commit to scv119/ray that referenced this pull request Jun 16, 2023
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
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.

None yet

2 participants