[pull] master from ray-project:master#4065
Merged
pull[bot] merged 4 commits intomiqdigital:masterfrom Apr 18, 2026
Merged
Conversation
## Description Necessary clean up before removing ExecutionPlan copy and deepcopy. ## Related issues #60358 ## Additional information N/A --------- Signed-off-by: Daniel Shin <kyuseung1016@gmail.com>
…62578) ## Description Adds a Cursor Bugbot rule to enforce the separation between unit tests (`python/ray/data/tests/unit/`) and integration tests (`python/ray/data/tests/`). The rule flags misplaced tests during PR review: - Tests in `unit/` that call `ray.*` APIs at runtime, use cluster-starting fixtures, or use `time.sleep()` → flagged as integration tests that should be moved out. - Tests in top-level files that make no runtime `ray.*` calls → suggested to move into `unit/`. This is a lighter-weight alternative to the pytest fixture/hook approach explored in #61505. ## Related issues Related to #61505 ## Additional information Doc-only change — only modifies `src/ray/.cursor/BUGBOT.md`. --------- Signed-off-by: Hyunoh-Yeo <hyunoh.yeo@gmail.com>
…gies (#62526) ## Description Follow up to #62306 per the discussion [here](#62306 (comment)). This change introduces a `chips_per_vm` override parameter to resolve ambiguity in TPU slice shapes (like v6e 2x4) where a topology can be provisioned as either a single 8-chip VM or multiple 4-chip VMs. This is an edge case for [v6e TPU topologies](https://docs.cloud.google.com/tpu/docs/v6e#configurations), but it would be useful to add an optional parameter to support it so that users can request their desired topology without mismatches in the number of bundles created by the `SlicePlacementGroup`. What we changed - Adjusted `get_chips_per_host` defaults to align with both v6e and v5e machine types. If # of chips is <= 8 with a sub or single-host topology, we should always just return the chip count. For chips > 8, these are multi-host configurations which are always 4 chips per host/VM. - Added a `chips_per_vm` parameter to `SlicePlacementGroup`. If provided, `chips_per_vm` is used to calculate the number of bundles to provision for the PG. Otherwise, we default to the expected number of hosts based on the topology. ## Related issues ## Additional information > Optional: Add implementation details, API changes, usage examples, screenshots, etc. --------- Signed-off-by: ryanaoleary <ryanaoleary@google.com> Signed-off-by: Ryan O'Leary <113500783+ryanaoleary@users.noreply.github.com>
After #62492 we no longer set CUDA_VISIBLE_DEVIES ="" when num_gpus=0 or not set. Torch if it detects that CUDA_VISIBLE_DEVIES ="" throws a runtime error, however now that CUDA_VISIBLE_DEVIES is not set at all it falls back to the nvidia driver to get the device ids. Following up on #62653 and instead checking for the default cuda:0 gpu id in these tests. --------- Signed-off-by: Joshua Lee <joshlee@anyscale.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )