[TRTLLM-9948][infra] Move to use FlexCache in Austin for 5080 nodes

[EmmaQiaoCh]

Summary by CodeRabbit

• Chores
  • Expanded GPU support in testing infrastructure to include RTX-5080 GPU nodes alongside existing support.

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.

[EmmaQiaoCh]

/bot run --stage-list "RTX5080-TensorRT-1, RTX5080-TensorRT-2"

[coderabbitai]

📝 Walkthrough

Walkthrough

The createKubernetesPodConfig function's FlexCache scratch NFS selection logic was updated to enable the Austin FlexCache-backed llmModelVolume for GPU node types containing either 6000d or rtx-5080, expanding from the previous 6000d-only condition.

Changes

Cohort / File(s)	Summary
GPU Node Type Condition jenkins/L0_Test.groovy	Updated conditional logic to include rtx-5080 alongside 6000d in FlexCache selection check; expanded accompanying comment to reflect both GPU types.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is entirely blank with no implementation details, test coverage, or checklist items completed.	Fill in the Description section explaining what changes were made and why. Document relevant test coverage and complete the PR Checklist items appropriately for this infrastructure change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: enabling FlexCache for RTX 5080 nodes in Austin, which matches the code modification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@jenkins/L0_Test.groovy`:
- Line 1776: Update the stale inline comment that mentions "rtx-pro-6000d, gh200
and rtx-5080" and FlexCache to reflect the current routing logic—remove
reference to "gh200" (since the code no longer routes gh200 to FlexCache) and
make the comment accurately describe which nodes are routed to FlexCache (e.g.,
"rtx-pro-6000d and rtx-5080 nodes are located in Austin DC; we use the FlexCache
to speed up data access"). Locate the comment near the routing condition that
references FlexCache and these node names and edit the text accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6e900923-3d63-4625-92f0-dd40a126300d

📥 Commits

Reviewing files that changed from the base of the PR and between f6db7e3 and c659694.

📒 Files selected for processing (1)

• jenkins/L0_Test.groovy

[tensorrt-cicd]

PR_Github #40900 [ run ] triggered by Bot. Commit: c659694 Link to invocation

[tensorrt-cicd]

PR_Github #40900 [ run ] completed with state SUCCESS. Commit: c659694
/LLM/main/L0_MergeRequest_PR pipeline #31901 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[EmmaQiaoCh]

/bot run --stage-list "RTX5080-TensorRT-1, RTX5080-TensorRT-2"

[tensorrt-cicd]

PR_Github #41177 [ run ] triggered by Bot. Commit: c659694 Link to invocation

[tensorrt-cicd]

PR_Github #41177 [ run ] completed with state SUCCESS. Commit: c659694
/LLM/main/L0_MergeRequest_PR pipeline #32141 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[EmmaQiaoCh]

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

[EmmaQiaoCh]

/bot run --stage-list "RTX5080-TensorRT-1, RTX5080-TensorRT-2" --disable-reuse-test

[EmmaQiaoCh]

/bot run --stage-list "RTX5080-TensorRT-1, RTX5080-TensorRT-2" --disable-reuse-test

[tensorrt-cicd]

PR_Github #41356 [ run ] triggered by Bot. Commit: c659694 Link to invocation

[tensorrt-cicd]

PR_Github #41356 [ run ] completed with state SUCCESS. Commit: c659694
/LLM/main/L0_MergeRequest_PR pipeline #32300 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[EmmaQiaoCh]

/bot run

[tensorrt-cicd]

PR_Github #41397 [ run ] triggered by Bot. Commit: c659694 Link to invocation

[tensorrt-cicd]

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

[EmmaQiaoCh]

/bot run

[tensorrt-cicd]

PR_Github #41565 [ run ] triggered by Bot. Commit: a376112 Link to invocation

[tensorrt-cicd]

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

[EmmaQiaoCh]

/bot run

[tensorrt-cicd]

PR_Github #42039 [ run ] triggered by Bot. Commit: 824d907 Link to invocation

[tensorrt-cicd]

PR_Github #42039 [ run ] completed with state SUCCESS. Commit: 824d907
/LLM/main/L0_MergeRequest_PR pipeline #32885 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

[EmmaQiaoCh]

The execution time is less than when we use the scratch in SC.
Failed stages in CI is not related with the PR changes. I'll merge the PR.