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] Place scheduler bazel targets into separate directories #52006

Merged
merged 2 commits into from
Apr 6, 2025

Conversation

Ziy1-Tan
Copy link
Contributor

@Ziy1-Tan Ziy1-Tan commented Apr 5, 2025

Why are these changes needed?

Related issue number

Closes #51987

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

@dentiny dentiny added the go add ONLY when ready to merge, run all tests label Apr 5, 2025
@Ziy1-Tan Ziy1-Tan force-pushed the subbazel_scheduler branch from b8d53aa to 5a9790f Compare April 5, 2025 02:39
@@ -14,14 +14,12 @@

#include "ray/raylet/scheduling/cluster_resource_manager.h"

#include <boost/algorithm/string.hpp>
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for cleaning up the dependency!

Signed-off-by: Ziy1-Tan <[email protected]>
@Ziy1-Tan Ziy1-Tan requested a review from dentiny April 5, 2025 09:08
Copy link
Contributor

@dentiny dentiny left a comment

Choose a reason for hiding this comment

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

LGMT, thanks for the effort and cleanup!

"//src/ray/common:id",
"//src/ray/common:network",
Copy link
Contributor

Choose a reason for hiding this comment

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

(just for my own curiosity) how did you get these dependencies sorted in alphabetical order?
Did you use linter in your IDE?

Copy link
Contributor Author

@Ziy1-Tan Ziy1-Tan Apr 5, 2025

Choose a reason for hiding this comment

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

Yes! Use buildifier and vscode-bazel together, deps will be sorted in order each time you save.

@dentiny
Copy link
Contributor

dentiny commented Apr 5, 2025

@aslonnie / @jjyao / @edoakes could you please help merge the PR? Thank you!

@jjyao jjyao merged commit ff3f0f3 into ray-project:master Apr 6, 2025
5 checks passed
pavelkushtia pushed a commit to pavelkushtia/ray that referenced this pull request Apr 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[core] Place scheduler bazel targets into separate directories
3 participants