reverse the amd ci test back to 1200s and split the 8-gpu deepseek job into two.#11238
Conversation
Summary of ChangesHello @sunxxuns, 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 standardizes the default timeout for continuous integration tests across all environments. It specifically reverts a previous adjustment that had increased the timeout for AMD (HIP) systems, ensuring a consistent 1200-second limit for the execution of each test file. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request reverts the timeout for AMD CI tests from 1500s back to 1200s, aligning it with the default timeout for other environments. The change simplifies the code by removing the conditional logic for the timeout value. My review includes a suggestion to add a comment explaining this change for future reference. It would also be helpful to fill out the pull request description to provide more context for the change.
| @@ -369,7 +369,7 @@ def auto_partition(files, rank, size): | |||
| arg_parser.add_argument( | |||
| "--timeout-per-file", | |||
| type=int, | |||
| default=1500 if is_hip() else 1200, | |||
| default=1200, | |||
There was a problem hiding this comment.
While simplifying the code is good, the context behind why the AMD-specific timeout is being removed is lost. Adding a brief comment would help future maintainers understand the history of this value, especially if timeout issues arise again on AMD platforms.
| default=1200, | |
| # The default timeout is 1200s. A longer timeout was temporarily used for AMD CI. | |
| default=1200, |
ec4d793 to
077ee6e
Compare
test/srt/run_suite.py
Outdated
| TestFile("test_deepseek_v3_basic.py", 150), | ||
| ], | ||
| "per-commit-8-gpu-amd-mtp": [ | ||
| TestFile("test_deepseek_v3_mtp.py", 150), |
There was a problem hiding this comment.
We do not need to split them into two suite. Just with two files should be good, because the timeout is per file.
.github/workflows/pr-test-amd.yml
Outdated
| @@ -290,7 +290,7 @@ jobs: | |||
| run: | | |||
| bash scripts/ci/amd_ci_exec.sh python3 run_suite.py --suite per-commit-2-gpu-amd | |||
|
|
|||
| unit-test-backend-8-gpu-amd: | |||
| unit-test-backend-8-gpu-amd-basic: | |||
There was a problem hiding this comment.
do not need to split into two jobs
| @@ -0,0 +1,77 @@ | |||
| import unittest | |||
There was a problem hiding this comment.
Splitting into two files is good!
2a34ed7 to
a34d5f2
Compare
a34d5f2 to
c23ca4c
Compare
…b into two. (sgl-project#11238) Co-authored-by: root <root@smci350-zts-gtu-e17-15.zts-gtu.dcgpu>
…b into two. (sgl-project#11238) Co-authored-by: root <root@smci350-zts-gtu-e17-15.zts-gtu.dcgpu>
Motivation
Modifications
Accuracy Tests
Benchmarking and Profiling
Checklist