Repository navigation
Create the trace directory in inductor_debug_cpu.py before exporting - #3992
Merged
Merged
Conversation
The profiling example exported Chrome traces to ./prof_trace, but nothing created that directory. The profiler logs an error and writes no file without raising, so the tutorial silently produced no traces, both for readers and in CI.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3992
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 4c3639d with merge base 5672cd9 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
huydhn
approved these changes
Nov 3, 2026
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.
The profiling example exported Chrome traces to ./prof_trace, but nothing created that directory. The profiler logs an error and writes no file without raising, so the tutorial silently produced no traces, both for readers and in CI.
We're also in the process of changing the profiler so that it will report an error; see pytorch/pytorch#203080. When that lands, this tutorial will start to fail.