Conversation
pytorchmergebot
pushed a commit
to pytorch/pytorch
that referenced
this pull request
May 1, 2026
Propose to add a "subgraph_name" entry to tlparse. After modifying tlparse like in meta-pytorch/tlparse#181, we will be able to see which subgraph the tlparse artifact is corresponding to. See meta-pytorch/tlparse#181 for tlparse result screenshots. Pull Request resolved: #181958 Approved by: https://github.com/anijain2305 ghstack dependencies: #181808, #181809, #181834
pytorchmergebot
pushed a commit
to pytorch/pytorch
that referenced
this pull request
May 8, 2026
Propose to add a "subgraph_name" entry to tlparse. After modifying tlparse like in meta-pytorch/tlparse#181, we will be able to see which subgraph the tlparse artifact is corresponding to. See meta-pytorch/tlparse#181 for tlparse result screenshots. Pull Request resolved: #181958 Approved by: https://github.com/anijain2305
angelayi
approved these changes
May 11, 2026
dsashidh
pushed a commit
to dsashidh/pytorch
that referenced
this pull request
May 13, 2026
Propose to add a "subgraph_name" entry to tlparse. After modifying tlparse like in meta-pytorch/tlparse#181, we will be able to see which subgraph the tlparse artifact is corresponding to. See meta-pytorch/tlparse#181 for tlparse result screenshots. Pull Request resolved: pytorch#181958 Approved by: https://github.com/anijain2305
Alokksinha00
pushed a commit
to Alokksinha00/pytorch
that referenced
this pull request
May 15, 2026
Propose to add a "subgraph_name" entry to tlparse. After modifying tlparse like in meta-pytorch/tlparse#181, we will be able to see which subgraph the tlparse artifact is corresponding to. See meta-pytorch/tlparse#181 for tlparse result screenshots. Pull Request resolved: pytorch#181958 Approved by: https://github.com/anijain2305 ghstack dependencies: pytorch#181808, pytorch#181809, pytorch#181834
Alokksinha00
pushed a commit
to Alokksinha00/pytorch
that referenced
this pull request
May 15, 2026
Propose to add a "subgraph_name" entry to tlparse. After modifying tlparse like in meta-pytorch/tlparse#181, we will be able to see which subgraph the tlparse artifact is corresponding to. See meta-pytorch/tlparse#181 for tlparse result screenshots. Pull Request resolved: pytorch#181958 Approved by: https://github.com/anijain2305
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
subgraph_namefield in PyTorch structured logs (used by regional inductor for repeated subgraphs, partitioned forward/backward subgraphs, etc.)subgraph_nameis present on a log entry, the HTML index renders a "Subgraph Name: ..." group header to visually separate artifacts by subgraphChanges
src/types.rs— Addsubgraph_name: Option<String>toEnvelopeso serde deserializes the new field. Addstarts_groupandgroup_nametoOutputFilefor rendering group separators.src/lib.rs— Thread the envelope'ssubgraph_namethroughadd_file_outputinto eachOutputFile. After all parsing, compute group boundaries by detecting when consecutive files have differentgroup_namevalues and settingstarts_group = true.src/parsers.rs— Copy the two newOutputFilefields in theCompilationMetricsParseroutput remapping.src/templates.rs— Render a<li>group header with top margin whenstarts_groupis true.tests/inputs/subgraph_name.log— Minimal 6-line test log with 3 artifacts: one with no subgraph, one withrepeated_subgraph0, one withpartitioned_bw_subgraph_1_0.tests/integration_test.rs—test_subgraph_name_grouping: verifies files are flat (no subgraph subdirectories), and the index HTML contains the expected group headers.Test plan
cargo test— all 64 tests pass (63 existing + 1 new)Example output:
For annotation based regional inductor:
For invoke_subgraph based regional inductor: