KEMBAR78
[TRTLLM-8201][feat] Topological graph helpers by greg-kwasniewski1 · Pull Request #8457 · NVIDIA/TensorRT-LLM · GitHub
Skip to content

Conversation

@greg-kwasniewski1
Copy link
Collaborator

@greg-kwasniewski1 greg-kwasniewski1 commented Oct 17, 2025

Description

This tiny PR does not introduce any "end-user" features, but it adds two helper functions predecessors and successors that are very helpful to detect and analyze subgraph patterns. They are continuously used for sharding analysis, and I believe it is useful to have them in the main branch, rather than recreating them for each new feature development.

Summary by CodeRabbit

  • New Features
    • Added utilities for analyzing tensor graph node relationships and dependencies. New functions support configurable depth-based traversal and optional filtering through include/exclude predicates, enabling flexible inspection of graph structures.

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.

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.

Signed-off-by: greg-kwasniewski1 <213329731+greg-kwasniewski1@users.noreply.github.com>
@greg-kwasniewski1 greg-kwasniewski1 requested a review from a team as a code owner October 17, 2025 08:34
@greg-kwasniewski1
Copy link
Collaborator Author

/bot run

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 17, 2025

📝 Walkthrough

Walkthrough

Two new utility functions added to node_utils.py for tensor graph analysis: predecessors() and successors(). Both recursively collect nodes up to a specified depth with optional include/exclude filtering predicates for traversing argument and user graphs respectively.

Changes

Cohort / File(s) Change Summary
Graph traversal utilities
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py
Added predecessors(node, depth=1, include=None, exclude=None) function to recursively collect predecessor nodes from node.args with depth-based traversal and filtering support. Added successors(node, depth=1, include=None, exclude=None) function to recursively collect successor nodes from node.users with identical depth and filtering capabilities.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description is incomplete and does not adequately follow the provided template. While the author has provided a clear and informative description section explaining what the helpers do and why they are useful for the codebase, two critical template sections are entirely unfilled: the Test Coverage section (which should list relevant tests safeguarding the changes) and the PR Checklist (which should indicate which items were reviewed). These are not minor omissions—the template explicitly marks test coverage as important for ensuring sufficient coverage, and the checklist is part of the required pre-submission review process.
Docstring Coverage ⚠️ Warning Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title Check ✅ Passed The PR title "[TRTLLM-8201][feat] Topological graph helpers" is clearly related to the main change in the changeset, which adds two new utility functions (predecessors() and successors()) for analyzing tensor graph topology. The title follows the required JIRA ticket format with the appropriate "[feat]" type designation. While the title is somewhat generic, it accurately conveys the addition of graph analysis helper utilities and is specific enough for teammates to understand the primary change when scanning history.
✨ 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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py (1)

1-1: Add required NVIDIA Apache-2.0 copyright header.

Per coding guidelines, all Python source files must include the NVIDIA Apache-2.0 copyright header with the current year (2025) at the top.

Add the copyright header before the module docstring:

# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: Apache-2.0
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

"""Common utils for torch fx graph transformation."""
🧹 Nitpick comments (1)
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py (1)

453-457: Enhance docstrings to follow Google-style format.

Per coding guidelines, use Google-style docstrings with Args, Returns, and Examples sections. The current docstrings lack parameter documentation and don't clarify the recursion behavior when nodes are filtered.

Example for predecessors:

"""
Build predecessor tree by recursively traversing node.args up to specified depth.

Args:
    node: The starting node for traversal.
    depth: Maximum recursion depth (default: 1). Use depth=1 to get immediate predecessors only.
    include: Optional predicate to filter nodes. Only nodes satisfying this condition are included.
    exclude: Optional predicate to filter nodes. Nodes satisfying this condition are excluded.

Returns:
    List of predecessor nodes that pass the include/exclude filters.

Note:
    Recursion does not traverse through excluded or non-included nodes.
"""

Also applies to: 478-482

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e72ade3 and 88a485f.

📒 Files selected for processing (1)
  • tensorrt_llm/_torch/auto_deploy/utils/node_utils.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{h,hpp,hh,hxx,cpp,cxx,cc,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Use only spaces, no tabs; indent with 4 spaces.

Files:

  • tensorrt_llm/_torch/auto_deploy/utils/node_utils.py
**/*.py

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+.
Indent Python code with 4 spaces; do not use tabs.
Maintain module namespace when importing; prefer 'from package.subpackage import foo' then 'foo.SomeClass()' instead of importing the class directly.
Python filenames should be snake_case (e.g., some_file.py).
Python classes use PascalCase names.
Functions and methods use snake_case names.
Local variables use snake_case; prefix 'k' for variables that start with a number (e.g., k_99th_percentile).
Global variables use upper SNAKE_CASE prefixed with 'G' (e.g., G_MY_GLOBAL).
Constants use upper SNAKE_CASE (e.g., MY_CONSTANT).
Avoid shadowing variables from an outer scope.
Initialize all externally visible members of a class in the constructor.
Prefer docstrings for interfaces that may be used outside a file; comments for in-function or file-local interfaces.
Use Google-style docstrings for classes and functions (Sphinx-parsable).
Document attributes and variables inline so they render under the class/function docstring.
Avoid reflection when a simpler, explicit approach suffices (e.g., avoid dict(**locals()) patterns).
In try/except, catch the most specific exceptions possible.
For duck-typing try/except, keep the try body minimal and use else for the main logic.

Files:

  • tensorrt_llm/_torch/auto_deploy/utils/node_utils.py
**/*.{cpp,cxx,cc,h,hpp,hh,hxx,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Prepend the NVIDIA Apache-2.0 copyright header with current year to the top of all source files (e.g., .cpp, .h, .cu, .py).

Files:

  • tensorrt_llm/_torch/auto_deploy/utils/node_utils.py
🧬 Code graph analysis (1)
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py (2)
tensorrt_llm/_torch/auto_deploy/custom_ops/attention_interface.py (1)
  • args (252-254)
tensorrt_llm/_torch/auto_deploy/shim/interface.py (1)
  • args (23-25)
🪛 Ruff (0.14.0)
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py

450-450: PEP 484 prohibits implicit Optional

Convert to T | None

(RUF013)


451-451: PEP 484 prohibits implicit Optional

Convert to T | None

(RUF013)


475-475: PEP 484 prohibits implicit Optional

Convert to T | None

(RUF013)


476-476: PEP 484 prohibits implicit Optional

Convert to T | None

(RUF013)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Pre-commit Check
🔇 Additional comments (1)
tensorrt_llm/_torch/auto_deploy/utils/node_utils.py (1)

472-492: Logic is correct, but ensure consistency with predecessors after its fix.

The filtering logic here correctly skips nodes that don't pass include/exclude checks and doesn't recurse into them. After fixing the predecessors function, verify both functions have consistent behavior.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21683 [ run ] triggered by Bot

Signed-off-by: greg-kwasniewski1 <213329731+greg-kwasniewski1@users.noreply.github.com>
@greg-kwasniewski1
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21696 [ run ] triggered by Bot. Commit: fc045e1

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21683 [ run ] completed with state ABORTED
LLM/main/L0_MergeRequest_PR #16338 (Blue Ocean) completed with status: ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21696 [ run ] completed with state SUCCESS. Commit: fc045e1
/LLM/main/L0_MergeRequest_PR pipeline #16348 completed with status: 'FAILURE'

@lucaslie lucaslie enabled auto-merge (squash) October 17, 2025 13:23
@lucaslie
Copy link
Member

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21706 [ run ] triggered by Bot. Commit: fc045e1

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21706 [ run ] completed with state SUCCESS. Commit: fc045e1
/LLM/main/L0_MergeRequest_PR pipeline #16356 completed with status: 'SUCCESS'

@lucaslie lucaslie merged commit bb7fdce into NVIDIA:main Oct 17, 2025
5 checks passed
govind-ramnarayan pushed a commit to nv-auto-deploy/TensorRT-LLM that referenced this pull request Oct 21, 2025
Signed-off-by: greg-kwasniewski1 <213329731+greg-kwasniewski1@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.

3 participants