Skip to content

[CI] Revert the C8 configuration for some test cases - #17505

Open
kunpengW-code wants to merge 1 commit into
vllm-project:mainfrom
kunpengW-code:fix-c8-yaml
Open

kunpengW-code wants to merge 1 commit into
vllm-project:mainfrom
kunpengW-code:fix-c8-yaml

Conversation

@kunpengW-code

@kunpengW-code kunpengW-code commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

What this PR does / why we need it?

In PR #15514, the startup configuration for C8 was updated. Some test cases still referenced the old configuration, so revert those test case changes.

This PR reverts the C8 configuration (specifically --kv-cache-dtype int8 and --attention_config.indexer_kv_dtype int8) for several GLM-5.1 and GLM-5.2 test cases. It also updates the documentation to use fp8 instead of int8 for GLM-5/5.1 on 950DT Products, and removes the int8 KV cache dtype configuration for GLM-5.2 where it is not recommended or has known issues.

Does this PR introduce any user-facing change?

No, this is a test configuration and documentation update.

How was this patch tested?

Tested via existing E2E nightly and weekly multi-node CI pipelines.

@gemini-code-assist

Copy link
Copy Markdown
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 updates several test configurations and documentation files by removing the --kv-cache-dtype int8 flag. Additionally, it updates the KV cache data type to fp8 for GLM5 models, ensuring consistency and alignment with current testing requirements.

Highlights

  • Configuration Reversion: Removed the --kv-cache-dtype int8 flag from multiple end-to-end test configuration files and tutorial documentation.
  • Data Type Update: Updated the KV cache and indexer KV data types to fp8 in the GLM5 model documentation.
New Features

🧠 You can now enable Memory (public preview) 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 the 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 counterproductive. 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.

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

@kunpengW-code
kunpengW-code requested review from lcfenglinwan and removed request for LCAIZJ and Yikun September 24, 2026 11:01

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

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.

Code Review

This pull request updates the configuration for GLM models across documentation and end-to-end test files. Specifically, it removes the --kv-cache-dtype int8 and --attention_config.indexer_kv_dtype int8 parameters from GLM-5.1 and GLM-5.2 configurations, and switches the KV cache data type from int8 to fp8 in the GLM-5 documentation. The reviewer provided a structured PR title and summary suggestion that aligns with the repository's style guide.

Comment thread docs/source/tutorials/models/GLM5.2.md
@github-actions github-actions Bot added documentation Improvements or additions to documentation module:tests labels Sep 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

  • A PR should do only one thing, smaller PRs enable faster reviews.
  • Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
  • Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

@kunpengW-code

kunpengW-code commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

@lcfenglinwan lcfenglinwan left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@kunpengW-code

kunpengW-code commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

@kunpengW-code

kunpengW-code commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

@kunpengW-code

kunpengW-code commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

@kunpengW-code

kunpengW-code commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

Signed-off-by: wangkunpeng <1289706727@qq.com>
@kunpengW-code

kunpengW-code commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator Author

/nightly multi-node-GLM-5.1-W8A8C8-A3_128k_90_50
nightly command triggered.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

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 merge-conflicts module:tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants