Skip to content

Conversation

@tqchen
Copy link
Member

@tqchen tqchen commented Jan 13, 2026

This PR introduces release extra tests to help run some integration of downstream packages, making it easy to run quick checks during release.

This PR introduces release extra tests to help run some integration
of downstream packages, making it easy to run quick checks during release.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @tqchen, 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 establishes a dedicated suite of "extra" integration tests (tests/release-extra) intended for use during release processes. The goal is to facilitate rapid compatibility checks with downstream packages, ensuring a smoother release by catching potential integration issues early. These tests are distinct from continuous integration and focus on representative use cases.

Highlights

  • New Release Test Suite: A new directory tests/release-extra has been introduced to house additional integration tests specifically designed for release verification.
  • Integration Test Purpose: These tests aim to provide quick checks for integration compatibility with downstream packages during release cycles, complementing existing unit and downstream tests.
  • cute DSL Compilation Test: A new test file test_cute_dsl_compile.py has been added, demonstrating the compilation and execution of cutlass.cute DSL kernels with torch tensors, including validation for tensor divisibility.

🧠 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
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 PR introduces a new set of extra tests for release validation, including a README and an initial test for cute DSL compilation. The new test is a good addition, but it can be improved by adding result verification and marking its dependency on CUDA to ensure it's skipped when CUDA is not available. I've provided a suggestion to update the test function accordingly.

@tqchen tqchen closed this Jan 13, 2026
@junrushao
Copy link
Member

I do think it's a good idea to test out those unittests per commit on mainline. Just need some test machines

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