Skip to content

Update test README with CI registry documentation and 5090/H100 guidance#17368

Merged
Kangyan-Zhou merged 1 commit intomainfrom
docs/update-test-readme-ci-guidance
Jan 23, 2026
Merged

Update test README with CI registry documentation and 5090/H100 guidance#17368
Kangyan-Zhou merged 1 commit intomainfrom
docs/update-test-readme-ci-guidance

Conversation

@alisonshao
Copy link
Copy Markdown
Collaborator

Summary

  • Expand CI Registry section with comprehensive registration function examples
  • Add guidance for choosing between 1-GPU suites: stage-b-test-small-1-gpu (5090) vs stage-b-test-large-1-gpu (H100)
  • Document decision criteria for when tests should use H100 instead of 5090
  • List all available per-commit (CUDA/AMD) and nightly suites
  • Add run_suite.py usage examples with auto-partitioning

Test plan

  • Documentation only change, no tests required

- Expand CI Registry section with registration function examples
- Add guidance for choosing between 1-GPU suites (5090 vs H100)
- Document when to use stage-b-test-small-1-gpu (5090) vs stage-b-test-large-1-gpu (H100)
- List available per-commit and nightly suites
- Add run_suite.py usage examples
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jan 19, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @alisonshao, 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 significantly enhances the documentation for the CI testing system by providing clearer guidelines and examples for test registration, suite selection, and execution. The updates aim to improve developer understanding of the testing infrastructure, particularly regarding GPU hardware choices for 1-GPU tests and the various available test suites, ensuring more efficient and appropriate test configuration.

Highlights

  • Expanded CI Registry Documentation: The CI registry section in test/README.md has been significantly expanded to include more comprehensive examples for registering tests across different backends (CUDA, AMD, CPU, NPU) and for various test configurations (per-commit, nightly, multi-backend, disabled tests).
  • 1-GPU Suite Guidance (5090 vs H100): New detailed guidance has been added to help users choose between the stage-b-test-small-1-gpu (RTX 5090) and stage-b-test-large-1-gpu (H100) suites. This includes a decision matrix based on architecture compatibility, memory requirements, and known 5090 limitations.
  • Comprehensive Suite Listing: The README now includes a complete list of all available per-commit (CUDA and AMD) and nightly test suites, providing a clearer overview of the testing infrastructure.
  • run_suite.py Usage Examples: Practical examples for using run_suite.py have been added, demonstrating how to execute per-commit, nightly, and auto-partitioned tests.

🧠 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.

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
Copy Markdown
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 significantly improves the test documentation by adding detailed guidance on the CI registry system, criteria for selecting GPU suites (5090 vs. H100), and usage examples for run_suite.py. The changes are clear, well-structured, and will be very helpful for developers. I have a couple of minor suggestions to further enhance clarity and maintainability.

Comment thread test/README.md
- `stage-a-test-1`, `stage-b-test-small-1-gpu-amd`, `stage-b-test-large-2-gpu-amd`

**Nightly**:
- `nightly-1-gpu`, `nightly-2-gpu`, `nightly-4-gpu`, `nightly-8-gpu`, etc.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The use of "etc." is a bit vague and can become outdated. To improve maintainability and provide a single source of truth, consider removing "etc." and adding a note that directs users to the NIGHTLY_SUITES dictionary in test/run_suite.py for the complete and up-to-date list.

Suggested change
- `nightly-1-gpu`, `nightly-2-gpu`, `nightly-4-gpu`, `nightly-8-gpu`, etc.
- `nightly-1-gpu`, `nightly-2-gpu`, `nightly-4-gpu`, `nightly-8-gpu`, and more. See `test/run_suite.py` for the full list.

Comment thread test/README.md
Comment on lines +114 to +117
# Run per-commit tests
python test/run_suite.py --hw cuda --suite stage-b-test-small-1-gpu

# Run nightly tests
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The comments in these examples are a bit too general. For instance, # Run per-commit tests is used for a command that runs a specific suite, not all of them. Making the comments more specific would improve clarity for developers using these examples.

Suggested change
# Run per-commit tests
python test/run_suite.py --hw cuda --suite stage-b-test-small-1-gpu
# Run nightly tests
# Run a specific per-commit suite
python test/run_suite.py --hw cuda --suite stage-b-test-small-1-gpu
# Run a specific nightly suite

@Kangyan-Zhou Kangyan-Zhou merged commit 1e8e0cc into main Jan 23, 2026
58 of 64 checks passed
@Kangyan-Zhou Kangyan-Zhou deleted the docs/update-test-readme-ci-guidance branch January 23, 2026 00:29
Johnsonms pushed a commit to Johnsonms/sglang that referenced this pull request Feb 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants