Skip to content

[None][fix] Add AutoDeploy post-merge stages - #15418

Merged
hnover-nv merged 2 commits into
NVIDIA:mainfrom
hnover-nv:hnover/ad-post-merge-stages
Jul 1, 2026
Merged

[None][fix] Add AutoDeploy post-merge stages#15418
hnover-nv merged 2 commits into
NVIDIA:mainfrom
hnover-nv:hnover/ad-post-merge-stages

Conversation

@hnover-nv

@hnover-nv hnover-nv commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Tests
    • Enhanced post-merge testing pipeline with additional automated test stages for comprehensive validation.
    • Updated performance testing configuration for improved accuracy across hardware variants.

Description

Add missing AutoDeploy post-merge Jenkins stages for test-db blocks that already declare stage: post_merge and backend: autodeploy:

  • H100_PCIe-AutoDeploy-Post-Merge-1 for l0_h100
  • DGX_B200-AutoDeploy-Post-Merge-1 for l0_b200
  • DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1 for l0_dgx_b200

These mirror the existing pre-merge AutoDeploy stage configurations for the same YAML files and GPU counts. Without these stages, the corresponding post-merge AutoDeploy test-db blocks are present but not selected by Jenkins unless the same tests also appear in another reachable block.

Also remove one duplicate 4-GPU B200 AutoDeploy perf sanity entry from the post-merge block. That test remains in the pre-merge AutoDeploy block, which is also run during post-merge, so keeping it in both places would make it run twice after this PR makes the post-merge block reachable.

After enabling the previously unreachable B200 AutoDeploy post-merge blocks, PR CI exposed an existing Nano NVFP4 accuracy failure:

  • accuracy/test_llm_api_autodeploy.py::TestNemotronNanoV3::test_accuracy[nvfp4-1-attn_dp_off-trtllm]: GSM8K accuracy below threshold.

This PR temporarily waives that test so the stage wiring fix can land while the underlying accuracy regression is investigated separately. The comparable pre-move single-GPU test previously ran as test_accuracy[nvfp4-1-trtllm]; the newer pytest id comes from the later attention-DP parameter split.

Test Coverage

  • Ran a local one-off reachability check over jenkins/L0_Test.groovy and tests/integration/test_lists/test-db/*.yml for AutoDeploy post-merge blocks.
    • Before this fix: 3 missing AutoDeploy post-merge blocks.
    • After this fix: 5 matched AutoDeploy post-merge blocks, 0 missing.
  • Checked pre/post duplicate overlap for the newly covered AutoDeploy stage shapes:
    • l0_h100.yml, 1 GPU: 0 overlapping tests.
    • l0_b200.yml, 1 GPU: 0 overlapping tests.
    • l0_dgx_b200.yml, 4 GPUs: 0 overlapping tests after removing the duplicate perf sanity entry.
  • Parsed tests/integration/test_lists/test-db/l0_dgx_b200.yml with PyYAML after editing.
  • Ran ./scripts/check_test_list.py --check-duplicate-waives.
  • Remote PR CI was run with:
    • /bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"
    • Build #43691 selected the new post-merge stages and exposed the waived 1-GPU Nano NVFP4 accuracy failure.

No runtime CI was run locally; this is a Jenkins stage mapping, test-list cleanup, and temporary waive change.

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)

  • If PR introduces API changes, an appropriate PR label is added - either api-compatible or api-breaking. For api-breaking, include BREAKING in the PR title.

  • 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

To see a list of available CI bot commands, please comment /bot help.

@hnover-nv hnover-nv changed the title [None][infra] Add AutoDeploy post-merge stages [None][fix] Add AutoDeploy post-merge stages Jun 16, 2026
@hnover-nv
hnover-nv force-pushed the hnover/ad-post-merge-stages branch 2 times, most recently from 37f9c2a to df21810 Compare June 16, 2026 18:18
@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --post-merge

@hnover-nv
hnover-nv marked this pull request as ready for review June 16, 2026 18:32
@hnover-nv
hnover-nv requested a review from a team June 16, 2026 18:32
@hnover-nv
hnover-nv requested a review from a team as a code owner June 16, 2026 18:32
@hnover-nv
hnover-nv requested review from tburt-nv and yiqingy0 June 16, 2026 18:32
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Three new post-merge AutoDeploy stage mappings are added to launchTestJobs() in the Jenkins pipeline for H100 PCIe and DGX B200 (both single and 4-GPU configurations). Additionally, the 4-GPU DGX B200 AutoDeploy perf sanity test list replaces the super_ad aggregated upload variant with the super_mtp_ad variant.

Changes

AutoDeploy Post-Merge CI Configuration

Layer / File(s) Summary
New Jenkins post-merge AutoDeploy stage mappings
jenkins/L0_Test.groovy
Adds H100_PCIe-AutoDeploy-Post-Merge-1 (x86, h100-cr, l0_h100, split 1,1), DGX_B200-AutoDeploy-Post-Merge-1 (x86 SLURM, auto:dgx-b200-flex, l0_b200, split 1,1,1,1), and DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1 (x86 SLURM, auto:dgx-b200-flex, l0_dgx_b200, split 1,1,4,1) to launchTestJobs().
DGX B200 4-GPU perf sanity test variant swap
tests/integration/test_lists/test-db/l0_dgx_b200.yml
Replaces the aggr_upload-super_ad_blackwell-super_ad_ws4_1k1k test_e2e variant with aggr_upload-super_mtp_ad_blackwell-super_mtp_ad_ws4_1k1k in the 4-GPU post_merge AutoDeploy perf sanity block.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The PR title clearly and concisely describes the main change: adding AutoDeploy post-merge stages. It follows the required format [None][fix] and accurately reflects the primary objective of the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The PR includes clear Description, Test Coverage, and Checklist sections and explains what changed and why.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #54654 [ run ] triggered by Bot. Commit: df21810 Link to invocation

@tburt-nv

Copy link
Copy Markdown
Collaborator

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tburt-nv

Copy link
Copy Markdown
Collaborator

#15418 (comment) would launch the entire post-merge pipeline, but we only need to run these stages.

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #54660 [ run ] triggered by Bot. Commit: df21810 Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

#15418 (comment) would launch the entire post-merge pipeline, but we only need to run these stages.

I wanted to make sure the normal post-merge pipeline picked the stages up. While it should be enough the stages exist, it seemed possible something else was mis-wired so that they could be directly invoked but would not auto-run. but if you think it looks ok and we just need to check that the tests are still green (they were off for a week or two) then that's find with me, we can check manually next week or whatever that they ran.

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #54654 [ run ] completed with state ABORTED. Commit: df21810

Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #54660 [ run ] completed with state FAILURE. Commit: df21810
/LLM/main/L0_MergeRequest_PR pipeline #43691 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv
hnover-nv force-pushed the hnover/ad-post-merge-stages branch from df21810 to 0b1f948 Compare June 16, 2026 23:49
@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --disable-fail-fast

@github-actions

Copy link
Copy Markdown

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component Vulnerability Description Severity
pytorch CVE-2025-3000 A vulnerability classified as critical has been found in PyTorch 2.6.0. This affects the function torch.jit.script. The manipulation leads to memory corruption. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. MEDIUM

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #55073 [ run ] triggered by Bot. Commit: b0dbcce Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #55073 [ run ] completed with state FAILURE. Commit: b0dbcce
/LLM/main/L0_MergeRequest_PR pipeline #44060 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@github-actions

Copy link
Copy Markdown

⚠️ Bot command ignored: The /bot command must appear at the very beginning of the comment (no leading blank lines or spaces). Please post a new comment with /bot as the first character.

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #55152 [ run ] triggered by Bot. Commit: 000fbce Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56440 [ kill ] completed with state SUCCESS. Commit: 0644801
Successfully killed previous jobs for commit 0644801

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56443 [ run ] triggered by Bot. Commit: 0644801 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56443 [ run ] completed with state FAILURE. Commit: 0644801
/LLM/main/L0_MergeRequest_PR pipeline #45285 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56459 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56459 [ run ] completed with state FAILURE. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45300 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

2 similar comments
@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "H100_PCIe-AutoDeploy-Post-Merge-1,DGX_B200-AutoDeploy-Post-Merge-1,DGX_B200-4_GPUs-AutoDeploy-Post-Merge-1"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56524 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56524 [ run ] completed with state SUCCESS. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45362 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56662 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56662 [ run ] completed with state FAILURE. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45486 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56674 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56674 [ run ] completed with state SUCCESS. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45497 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56704 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56704 [ run ] completed with state SUCCESS. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45527 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@hnover-nv

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56826 [ run ] triggered by Bot. Commit: acb1d19 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #56826 [ run ] completed with state SUCCESS. Commit: acb1d19
/LLM/main/L0_MergeRequest_PR pipeline #45642 completed with status: 'SUCCESS'

CI Report

Link to invocation

@hnover-nv
hnover-nv merged commit 4cfcc64 into NVIDIA:main Jul 1, 2026
10 checks passed
evezhier pushed a commit to evezhier/TensorRT-LLM that referenced this pull request Jul 2, 2026
Signed-off-by: Harris Nover <249353502+hnover-nv@users.noreply.github.com>
@hnover-nv
hnover-nv deleted the hnover/ad-post-merge-stages branch July 7, 2026 22:05
BrianLi23 pushed a commit to BrianLi23/TensorRT-LLM that referenced this pull request Jul 9, 2026
Signed-off-by: Harris Nover <249353502+hnover-nv@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants