[None][chore] Weekly mass integration of release/1.2 - #11572
Conversation
ec2e14b to
514411d
Compare
|
/bot run |
📝 WalkthroughWalkthroughThis pull request removes the TRITON MOE backend option from test parameterizations and updates test configurations to use W4A16 MXFP4 variants instead of W4A8 MXFP4, while also renaming a test utility parameter and removing an obsolete test waiver entry. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
|
/bot run |
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@tests/integration/test_lists/qa/llm_function_core.txt`:
- Line 149: Confirm that the test entry
accuracy/test_llm_api_pytorch.py::TestQwen3_30B_A3B::test_w4a16_mxfp4[latency-TRITON]
in tests/integration/test_lists/qa/llm_function_core.txt exactly matches the
validated entry in llm_function_core_sanity.txt: verify the test function name
test_w4a16_mxfp4 and the test class TestQwen3_30B_A3B exist in
accuracy/test_llm_api_pytorch.py and that the "[latency-TRITON]" marker is a
valid parameterization; if anything differs, update the entry in
llm_function_core.txt to match the canonical line in
llm_function_core_sanity.txt (or add the missing test/function to
accuracy/test_llm_api_pytorch.py if the test is absent).
|
/bot run |
|
PR_Github #36182 [ run ] triggered by Bot. Commit: |
|
PR_Github #36182 [ run ] completed with state
|
|
/bot run |
|
PR_Github #36251 [ run ] triggered by Bot. Commit: |
|
PR_Github #36251 [ run ] completed with state
|
4f23f3b to
15f494a
Compare
|
/bot run |
|
PR_Github #36258 [ run ] triggered by Bot. Commit: |
|
PR_Github #36258 [ run ] completed with state
|
15f494a to
77390e3
Compare
|
/bot run |
|
PR_Github #36263 [ run ] triggered by Bot. Commit: |
|
PR_Github #36263 [ run ] completed with state
|
|
/bot run |
|
PR_Github #36281 [ run ] triggered by Bot. Commit: |
|
PR_Github #36281 [ run ] completed with state
|
589b772 to
2837103
Compare
|
/bot run |
|
PR_Github #36340 [ run ] triggered by Bot. Commit: |
|
PR_Github #36340 [ run ] completed with state |
2837103 to
d37f1d6
Compare
d37f1d6 to
167e8aa
Compare
|
/bot skip --comment "CI already passed" |
|
PR_Github #36383 [ skip ] triggered by Bot. Commit: |
|
PR_Github #36383 [ skip ] completed with state |
167e8aa to
e94e5e1
Compare
|
Added more PRs per offline discussion. |
e94e5e1 to
eedb211
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #36540 [ run ] triggered by Bot. Commit: |
|
PR_Github #36540 [ run ] completed with state
|
Signed-off-by: Lizhi Zhou <1432185+reasonsolo@users.noreply.github.com> Signed-off-by: Mike Iovine <miovine@nvidia.com>
…VIDIA#11495) Signed-off-by: Dongfeng Yu <dongfengy@nvidia.com> Signed-off-by: Mike Iovine <miovine@nvidia.com>
…DIA#11543) Signed-off-by: Patrice Castonguay <55748270+pcastonguay@users.noreply.github.com> Signed-off-by: Mike Iovine <miovine@nvidia.com>
NVIDIA#11383) Signed-off-by: Junyi Xu <219237550+JunyiXu-nv@users.noreply.github.com> Signed-off-by: Mike Iovine <miovine@nvidia.com>
Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com> Signed-off-by: Mike Iovine <miovine@nvidia.com>
eedb211 to
78e49d1
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #36550 [ run ] triggered by Bot. Commit: |
|
PR_Github #36550 [ run ] completed with state |
Description
Weekly round of mass integration from release branch.
Skipped:
Test Coverage
N/A
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...Provide a user friendly way for developers to interact with a Jenkins server.
Run
/bot [-h|--help]to print this help message.See details below for each supported subcommand.
Details
run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]Launch build/test pipelines. All previously running jobs will be killed.
--reuse-test (optional)pipeline-id(OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.--disable-reuse-test(OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.--disable-fail-fast(OPTIONAL) : Disable fail fast on build/tests/infra failures.--skip-test(OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.--stage-list "A10-PyTorch-1, xxx"(OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.--gpu-type "A30, H100_PCIe"(OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.--test-backend "pytorch, cpp"(OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.--only-multi-gpu-test(OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.--disable-multi-gpu-test(OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.--add-multi-gpu-test(OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.--post-merge(OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx"(OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".--detailed-log(OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.--debug(OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in thestage-listparameter to access the appropriate container environment. Note: Does NOT update GitHub check status.For guidance on mapping tests to stage names, see
docs/source/reference/ci-overview.mdand the
scripts/test_to_stage_mapping.pyhelper.kill
killKill all running builds associated with pull request.
skip
skip --comment COMMENTSkip testing for latest commit on pull request.
--comment "Reason for skipping build/test"is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.reuse-pipeline
reuse-pipelineReuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.
Summary by CodeRabbit