fix little batchsize and int8 quant on ci

[zhuyutong332]

fix little batchsize and int8 quant
add actuation commands of test_intranode.py which num-tokens=2 and test_low_latency.py which num-tokens=1/2,
Added the case where dispatch_use_fp8 is set to false in the test_low_latency.py file.

[gemini-code-assist]

Summary of Changes

Hello @z30065, I'm Gemini Code Assist¹! 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 robustness of the continuous integration (CI) tests by modifying the test_low_latency function. The primary goal is to ensure that the low-latency dispatch functionality is correctly validated with and without FP8 quantization, preventing potential regressions and improving the reliability of the system's performance under various data precision configurations.

Highlights

• Expanded Test Coverage: The test_low_latency function now executes its core logic twice: once with FP8 (8-bit floating point) quantization enabled and once with it disabled. This ensures comprehensive testing of the low-latency dispatch mechanism under both scenarios.
• CI Robustness: This change directly addresses and fixes issues related to int8 quant on CI, ensuring that the continuous integration pipeline thoroughly validates the system's behavior across different quantization settings.

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

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/pr-test-npu.yml

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

[gemini-code-assist]

Code Review

This pull request extends a test to cover both FP8 and non-FP8 paths by introducing a loop. However, this change introduces two issues. First, a state variable is not reset between loop iterations, making the test cases dependent. Second, the loop variable affects subsequent benchmarking code, causing it to only run for one of the two paths. I've provided a detailed comment with a suggestion to fix the first issue and an explanation for the second.