Skip to content

[rayapp] Test templates against different ray versions#453

Merged
elliot-barn merged 9 commits intomainfrom
elliot-barn-rayapp-test-ray-version
Mar 12, 2026
Merged

[rayapp] Test templates against different ray versions#453
elliot-barn merged 9 commits intomainfrom
elliot-barn-rayapp-test-ray-version

Conversation

@elliot-barn
Copy link
Collaborator

@elliot-barn elliot-barn commented Mar 10, 2026

Adding --ray-version flag to rayapp test

Tested against model-composition-recsys template
image

image

Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the rayapp testing utility by providing the capability to test templates against specific Ray versions. This allows developers to verify template compatibility and behavior across different Ray releases, improving the robustness and reliability of template deployments. The changes include adding a new command-line flag, implementing the core logic for version overriding, and integrating this functionality into the existing test execution flow.

Highlights

  • New Feature: Ray Version Override: Introduced a new --ray-version flag to the rayapp test command, allowing users to specify a target Ray version for template testing.
  • Core Logic for Version Override: Implemented a new overrideClusterEnvRayVersion function to dynamically modify the Ray version within cluster environments, supporting both BYOD and ImageURI configurations.
  • Integration with Test Runner: Updated RunAllTemplateTests and RunTemplateTest functions to accept the new rayVersion parameter, ensuring that the specified version is applied to templates during testing.
  • Expanded Test Coverage: Added new unit tests for the overrideClusterEnvRayVersion function and a comprehensive integration test to validate the end-to-end Ray version override functionality in the test runner.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • rayapp/rayapp/main.go
    • Added a new command-line flag --ray-version for the test subcommand.
    • Updated calls to RunAllTemplateTests and RunTemplateTest to pass the new rayVersion parameter.
    • Modified the usage message to include the new --ray-version flag.
  • rayapp/template.go
    • Implemented overrideClusterEnvRayVersion to create a new ClusterEnv with a specified Ray version.
    • Added logic within overrideClusterEnvRayVersion to handle both BYOD (Build Your Own Docker) and ImageURI cluster environments.
  • rayapp/template_test.go
    • Added TestOverrideClusterEnvRayVersion with test cases for overriding Ray versions in different ClusterEnv configurations (build_id, image_uri, BYOD).
  • rayapp/template_test_runner.go
    • Modified RunAllTemplateTests and RunTemplateTest to accept a rayVersion string parameter.
    • Updated the runTemplateTestsWithFilter function signature to include rayVersion.
    • Added logic within runTemplateTestsWithFilter to iterate through templates and apply the rayVersion override if provided.
  • rayapp/template_test_runner_test.go
    • Updated existing calls to runTemplateTestsWithFilter to pass an empty string for the new rayVersion parameter.
    • Added TestRunTemplateTestsWithRayVersionOverride to verify that the specified Ray version is correctly applied to the image URI during testing.
Activity
  • The author, elliot-barn, initiated this pull request to introduce a --ray-version flag to the rayapp test command.
  • The changes involve modifying the command-line argument parsing, adding new functions for version manipulation, and updating existing test execution logic.
  • New unit and integration tests were added to cover the introduced functionality.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

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 introduces a --ray-version flag to the rayapp test command, allowing templates to be tested against different Ray versions. The implementation correctly overrides the Ray version in the cluster environment for both BYOD and image-based setups. The changes are well-tested. I have one suggestion to improve the consistency of the new flag's description in the help message.

elliot-barn and others added 2 commits March 10, 2026 21:30
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
updating ray version flag desc

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Elliot Barnwell <elliot.barnwell@anyscale.com>
@elliot-barn elliot-barn marked this pull request as ready for review March 10, 2026 23:48
…project/rayci into elliot-barn-rayapp-test-ray-version
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
Copy link
Contributor

@sai-miduthuri sai-miduthuri left a comment

Choose a reason for hiding this comment

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

For some reason, the go fmt test is failing on CI. Is it a legitimate failure?

Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
@elliot-barn elliot-barn merged commit d036417 into main Mar 12, 2026
2 checks passed
@elliot-barn elliot-barn deleted the elliot-barn-rayapp-test-ray-version branch March 12, 2026 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants