update ci test

[ovowei]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ovowei, 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 focuses on enhancing the efficiency and reliability of the continuous integration (CI) test suite. It achieves this by optimizing resource allocation for specific benchmark tests and implementing robust handling of test runner exit codes, which is crucial for accurate pass/fail reporting in automated CI pipelines.

Highlights

• Resource Optimization for Benchmark Tests: The subpool_thread_count and CPUINFER_PARAM values have been reduced in the test_moe_amx_bench_int4.py and test_moe_amx_bench_int8.py files, likely to decrease resource consumption and execution time for these CI benchmarks.
• Improved CI Exit Code Handling: The run_suite.py script now correctly propagates the exit status of the run_unittest_files function to the system's exit code, ensuring that CI systems accurately reflect the success or failure of test runs.

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 aims to update the CI tests. It correctly modifies run_suite.py to propagate test failure exit codes, which is a good improvement for CI integration. I've suggested a small simplification to make the exit code handling more concise and robust. However, a critical issue is that two test files, test_moe_amx_bench_int4.py and test_moe_amx_bench_int8.py, contain unresolved merge conflict markers. These will cause syntax errors and must be resolved before this PR can be merged.

[gemini-code-assist]

This file contains unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>). These markers will cause a syntax error and must be removed. Please resolve the conflict and commit the correct version of the code.

    "subpool_thread_count": [30, 30],
}
CPUINFER_PARAM = 60

[gemini-code-assist]

This file contains unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>). These markers will cause a syntax error and must be removed. Please resolve the conflict and commit the correct version of the code.

    "subpool_thread_count": [30, 30],
}
CPUINFER_PARAM = 60

[gemini-code-assist]

The logic to convert the internal exit code to a standard shell exit code is correct. However, it can be simplified to be more robust and concise. The expression exit_code != 0 evaluates to False (which sys.exit treats as 0) for success and True (treated as 1) for any failure, which is more robust if the failure code ever changes from -1.

Suggested change

	exit_code = run_per_commit(hw, args.suite)
	# run_unittest_files returns 0 for success, -1 for failure
	# Convert to standard exit codes: 0 for success, 1 for failure
	sys.exit(0 if exit_code == 0 else 1)
	exit_code = run_per_commit(hw, args.suite)
	# run_unittest_files returns 0 for success, non-zero for failure.
	# Convert to standard exit codes: 0 for success, 1 for failure.
	sys.exit(exit_code != 0)