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

[ci] Reduce train tests+examples parallelism #38820

Merged
merged 2 commits into from
Aug 24, 2023

Conversation

krfricke
Copy link
Contributor

Why are these changes needed?

The "Train tests and examples" pipeline is being thinned out in scope of the storage API refactor. After #38759 was merged, one of the jobs doesn't contain any tests anymore. This is not correctly detected by the sharding script, so bazel complains about an empty test suite.

This PR reduces the parallelism of this job so that it's not empty anymore. This does not change any Ray code. (There's only a trivial change to trigger testing).

Screenshot 2023-08-24 at 10 31 54

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

Kai Fricke added 2 commits August 24, 2023 10:31
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Copy link
Contributor

@justinvyu justinvyu left a comment

Choose a reason for hiding this comment

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

Thanks!

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.

This is basically test only

@zhe-thoughts
Copy link
Collaborator

@matthewdeng can you give a green light here before I merge?

@@ -32,7 +32,7 @@
- label: ":steam_locomotive: Train tests and examples"
conditions: ["NO_WHEELS_REQUIRED", "RAY_CI_TRAIN_AFFECTED"]
instance_size: large
parallelism: 4
parallelism: 3
Copy link
Contributor

Choose a reason for hiding this comment

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

What's the end state here for 2.7? Are we going to delete this step once they're all moved to the new persistence path?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We aim to flick the switch to on per default and then remove the duplicate steps

@krfricke krfricke added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Aug 24, 2023
@zhe-thoughts zhe-thoughts merged commit 8ed1cd1 into ray-project:master Aug 24, 2023
41 of 44 checks passed
@krfricke krfricke deleted the ci/train-tests branch August 25, 2023 08:15
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
* [ci] Reduce train tests+examples parallelism

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
LeonLuttenberger pushed a commit to jaidisido/ray that referenced this pull request Sep 5, 2023
* [ci] Reduce train tests+examples parallelism

Signed-off-by: Kai Fricke <kai@anyscale.com>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
* [ci] Reduce train tests+examples parallelism

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Victor <vctr.y.m@example.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ray 2.7 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.

None yet

4 participants