Skip to content

Conversation

@aslonnie
Copy link
Collaborator

if a test is not stable, it should be on manual frequency. we will no longer treat unstable tests differently.

if a test is not stable, it should be on manual frequency.

Signed-off-by: Lonnie Liu <[email protected]>
@aslonnie aslonnie requested a review from a team as a code owner January 17, 2026 20:46
@aslonnie aslonnie requested review from dayshah and edoakes January 17, 2026 20:46
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request removes the stable field from test configurations and the associated logic that treats unstable tests differently. This is a good simplification, making the test stability handling more straightforward by relying on the frequency field (e.g., manual for unstable tests). The changes are applied consistently across Python code, YAML configurations, and tests. My review includes one suggestion to remove a now-unused method to further improve code maintainability.

I am having trouble creating individual review comments. Click here to see my feedback.

release/ray_release/test_automation/release_state_machine.py (70-73)

medium

With the removal of this logic, the Test.is_stable() method in release/ray_release/test.py appears to be unused and can be removed as part of this cleanup. This will improve code maintainability by removing dead code.

@aslonnie aslonnie added the go add ONLY when ready to merge, run all tests label Jan 17, 2026
@ray-gardener ray-gardener bot added core Issues that should be addressed in Ray Core devprod release-test release test labels Jan 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core devprod go add ONLY when ready to merge, run all tests release-test release test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant