[https://nvbugs/5997534][fix] AutoDeploy: Skip Eagle3 One Model Test on pre-Hopper

[govind-ramnarayan]

Eagle3 acceptance rate threshold (25%) in accuracy test is calibrated for H100s (with a generous leeway). Slightly lower acceptance rate than this on different (especially older) hardware is fine. The test is meant to verify that Eagle3 wrapper code is working properly in AutoDeploy, so we want to flag lower-than-expected acceptance rates on hardware, not guarantee that it performs well on all hardware.

Tested on an L20 in ComputeLab:

Running 1 items in this shard: accuracy/test_llm_api_autodeploy.py::TestLlama3_1_8B_Instruct_Eagle3::test_eagle3_one_model

tests/integration/defs/accuracy/test_llm_api_autodeploy.py::TestLlama3_1_8B_Instruct_Eagle3::test_eagle3_one_model SKIPPED (This test is not supported in pre-Hopper architecture)

Summary by CodeRabbit

Release Notes

• Tests
  • Updated test hardware requirements to properly skip on pre-Hopper hardware configurations.
  • Removed test waiver entry to enable proper test gating based on hardware capabilities.

Description

Test Coverage

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

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

[govind-ramnarayan]

/bot help

[github-actions]

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) --high-priority]

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 the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

--high-priority (OPTIONAL) : Run the pipeline with high priority. This option is restricted to authorized users only and will route the job to a high-priority queue.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip 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-pipeline

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: abe12db6-1664-49a1-ac78-788362a21e4c

📥 Commits

Reviewing files that changed from the base of the PR and between c3de562 and 718c512.

📒 Files selected for processing (2)

• tests/integration/defs/accuracy/test_llm_api_autodeploy.py
• tests/integration/test_lists/waives.txt

💤 Files with no reviewable changes (1)

• tests/integration/test_lists/waives.txt

---

📝 Walkthrough

Walkthrough

The changes migrate test-skipping logic from a waiver file entry to a code-level decorator for a specific test case. The import statement is updated to include the required skip decorator, which is then applied to the test method, and the corresponding waiver entry is removed.

Changes

Cohort / File(s)	Summary
Skip Logic Migration tests/integration/defs/accuracy/test_llm_api_autodeploy.py	Added @skip_pre_hopper decorator import and applied it to TestLlama3_1_8B_Instruct_Eagle3.test_eagle3_one_model, making the skip condition explicit in code.
Skip Logic Migration tests/integration/test_lists/waives.txt	Removed waiver entry for the test that now uses the code-level decorator instead of file-based waiving.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides context about why the change is needed (threshold calibrated for H100s) but lacks required sections like explicit Description, Test Coverage, and a properly filled PR Checklist per the template.	Add explicit Description and Test Coverage sections explaining the changes. Verify all PR Checklist items are appropriate and clearly checked/marked.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a skip decorator for the Eagle3 test on pre-Hopper GPUs and referencing the associated bug ticket.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #41773 [ run ] triggered by Bot. Commit: 718c512 Link to invocation

[tensorrt-cicd]

PR_Github #41773 [ run ] completed with state SUCCESS. Commit: 718c512
/LLM/main/L0_MergeRequest_PR pipeline #32669 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

Link to invocation

[govind-ramnarayan]

/bot run --disable-fail-fast

[govind-ramnarayan]

/bot run

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #42003 [ run ] triggered by Bot. Commit: f452c40 Link to invocation

[tensorrt-cicd]

PR_Github #42004 [ run ] triggered by Bot. Commit: f452c40 Link to invocation

[tensorrt-cicd]

PR_Github #42003 [ run ] completed with state ABORTED. Commit: f452c40

Link to invocation

[tensorrt-cicd]

PR_Github #42004 [ run ] completed with state SUCCESS. Commit: f452c40
/LLM/main/L0_MergeRequest_PR pipeline #32851 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

Link to invocation

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #42026 [ run ] triggered by Bot. Commit: f452c40 Link to invocation

[tensorrt-cicd]

PR_Github #42026 [ run ] completed with state SUCCESS. Commit: f452c40
/LLM/main/L0_MergeRequest_PR pipeline #32871 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

Link to invocation

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #42392 [ run ] triggered by Bot. Commit: abe398a Link to invocation

[tensorrt-cicd]

PR_Github #42392 [ run ] completed with state SUCCESS. Commit: abe398a
/LLM/main/L0_MergeRequest_PR pipeline #33168 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

Link to invocation

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #42561 [ run ] triggered by Bot. Commit: 5d07841 Link to invocation

[govind-ramnarayan]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #42660 [ run ] triggered by Bot. Commit: bdc1842 Link to invocation