-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update outdated docs for torch logs #3127
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3127
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 New FailureAs of commit 26d2b0e with merge base 0088d45 (): NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@ezyang could you please give me some feedbacks on this fix? |
@pytorchbot label "torch.compile" |
Didn't find following labels among repository labels: module: logging |
TBH, maybe we should introduce tlparse here, it's much better for looking at the output code bits. Description at https://docs.google.com/document/d/1y5CRfMLdwEoF1nTk9q8qEu1mgMUuUtvhklPKJ2emLU8/edit?tab=t.0#heading=h.u9711c2s6w0c |
Thank you! I'll take a look at it. |
waiting for render |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few editorial suggestions.
recipes_source/torch_logs.py
Outdated
separator("") | ||
###################################################################### | ||
# Use TORCH_TRACE/tlparse to produce produce compilation reports | ||
# ~~~~~~~~~~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# ~~~~~~~~~~ | |
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
recipes_source/torch_logs.py
Outdated
|
||
separator("") | ||
###################################################################### | ||
# Use TORCH_TRACE/tlparse to produce produce compilation reports |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Use TORCH_TRACE/tlparse to produce produce compilation reports | |
# Using ``TORCH_TRACE/tlparse`` to produce produce compilation reports |
recipes_source/torch_logs.py
Outdated
# Use TORCH_TRACE/tlparse to produce produce compilation reports | ||
# ~~~~~~~~~~ | ||
# | ||
# In this section, we introduce the usage of TORCH_TRACE and tlparse to produce reports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# In this section, we introduce the usage of TORCH_TRACE and tlparse to produce reports. | |
# In this section, we introduce ``TORCH_TRACE`` and ``tlparse`` to produce reports. |
recipes_source/torch_logs.py
Outdated
# ~~~~~~~~~~ | ||
# | ||
# In this section, we introduce the usage of TORCH_TRACE and tlparse to produce reports. | ||
# First, we run `TORCH_TRACE="/tmp/tracedir" python script.py` to generate the raw trace logs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# First, we run `TORCH_TRACE="/tmp/tracedir" python script.py` to generate the raw trace logs. | |
# | |
# 1. Generate the raw trace logs by running the following command: | |
# | |
# .. code-block:: bash | |
# | |
# TORCH_TRACE="/tmp/tracedir" python script.py` | |
# |
recipes_source/torch_logs.py
Outdated
# | ||
# In this section, we introduce the usage of TORCH_TRACE and tlparse to produce reports. | ||
# First, we run `TORCH_TRACE="/tmp/tracedir" python script.py` to generate the raw trace logs. | ||
# We have replace `/tmp/tracedir` with a path to a directory you want to store the trace logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# We have replace `/tmp/tracedir` with a path to a directory you want to store the trace logs | |
# Ensure you replace ``/tmp/tracedir`` with the path to the directory where you want to store the trace logs |
recipes_source/torch_logs.py
Outdated
# `pip install tlparse` and then `tlparse /tmp/tracedir`. This will open up your browser with | ||
# HTML like generated above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# `pip install tlparse` and then `tlparse /tmp/tracedir`. This will open up your browser with | |
# HTML like generated above. | |
# This will open your browser with the HTML-like generated above. | |
# |
recipes_source/torch_logs.py
Outdated
# `pip install tlparse` and then `tlparse /tmp/tracedir`. This will open up your browser with | ||
# HTML like generated above. | ||
# | ||
# By default, reports generated by `tlparse` are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# By default, reports generated by `tlparse` are | |
# By default, reports generated by ``tlparse`` are |
@ezyang hello. Do I need to make any more modifications for this issue? I see that the pipeline is still waiting to be reported. |
Fixes #137285
Description
Update Python code to better address the usage of python logging and
torch.compile
.Checklist
cc @williamwen42 @msaroufim @anijain2305