[None][ci] move all llama4 test cases to post merge

[QiJune]

Summary by CodeRabbit

• Tests

  • Refined integration test coverage by updating which precision/configuration variants run for select model scenarios.
  • Removed redundant test cases to streamline execution on targeted hardware profiles.
  • Ensures more focused and efficient validation without changing product behavior.

• Style

  • Minor formatting cleanup in test configuration files for consistency.

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

• 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 the stage-list parameter 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.md
and the scripts/test_to_stage_mapping.py helper.

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]

📝 Walkthrough

Walkthrough

Updates test selection YAMLs: l0_dgx_b200 swaps specific Llama4ScoutInstruct FP4/FP8 variants; l0_dgx_b300 removes two Llama4ScoutInstruct tests; l0_h100 normalizes whitespace. No code or control-flow changes outside test list adjustments.

Changes

Cohort / File(s)	Summary of Changes
DGX B200 Llama4ScoutInstruct variants tests/integration/test_lists/test-db/l0_dgx_b200.yml	Replaced specific TestLlama4ScoutInstruct entries: adjusted FP4 and FP8-chunked-prefill variants with updated tp/ep and cuda_graph combinations; other tests unchanged.
DGX B300 removals tests/integration/test_lists/test-db/l0_dgx_b300.yml	Removed two entries: test_fp8[tp4-cuda_graph=True] and test_fp4[tp4-cuda_graph=True] for TestLlama4ScoutInstruct.
H100 whitespace cleanup tests/integration/test_lists/test-db/l0_h100.yml	Removed a blank line in the pre_merge PyTorch block; no behavioral change.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [None][ci] move some llama4 test cases to pre merge #8189 — Modifies the same l0_dgx_b200 TestLlama4ScoutInstruct entries (FP4/FP8 variants), indicating direct overlap in test list adjustments.

Suggested reviewers

• mikeiovine

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description consists solely of the unmodified template, with no actual title, Description, or Test Coverage details provided. As a result there is no summary of the changes, rationale, or test plan. This fails to meet the repository’s PR description requirements.	Please fill in the PR title using the specified ticket and type format, provide a concise description of the changes and the reason behind them, and list the tests that cover these changes under Test Coverage. Additionally, confirm the PR checklist items or update them as appropriate. This will ensure the description meets the repository standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title correctly follows the repository’s “[ticket][type] Summary” format and concisely describes the primary change of moving all Llama4 test cases to post-merge CI stages, making it clear and relevant.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[QiJune]

/bot skip --comment "trivial changes"

[tensorrt-cicd]

PR_Github #21452 [ skip ] triggered by Bot

[tensorrt-cicd]

PR_Github #21452 [ skip ] completed with state SUCCESS
Skipping testing for commit a290f27