Merged
Conversation
The remaining Ray+Iris hybrid integration test has no production use case — drop it rather than keep a Ray-dependent test as the last ray_remote caller outside lib/fray/.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Deletes
tests/rl/integration/test_iris_integration.py, the lastimport raycaller intests/outsidelib/fray/. The test exercised a Ray+Iris hybrid that has no production use case; keeping it would forcelib/fray/v1and the fray v2 Ray backend to stay alive solely to keep this test importable.Test plan
./infra/pre-commit.py --all-files --fixcleanuv run pyrefly check— 164 errors, matches baseline (no new errors)rg '^\s*import ray\b|^\s*from ray\b' tests/→ zero hitsrg 'test_iris_integration' .github/ tests/ pyproject.toml→ zero hitsRelated: #4453, #4953