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
Add --timing
flag, phase timing to @dynamo_timed
#92637
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/92637
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 FailuresAs of commit cd1b009: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
torch/_dynamo/utils.py
Outdated
for key, time in timings.items(): | ||
total += time | ||
print(f" {key} : {time}") | ||
print(f"Total time: {total}s") |
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.
this is actually sus cause of nesting
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.
seems fine I guess
@pytorchbot merge -f "local lintrunner -a doesn't show a diff. lintrunner init run, still no dice. I give up. yolo" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
@pytorchbot revert -f "Broke lint" -c ignoredsignal |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot revert -m "Broke lint" -c ignoredsignal |
Not sure what was the point of doing this? If commit breaks CI it will be reverted, it's just the matter of time... |
btw some lints (like flake8) cannot be automatically fixed. So it is expected that |
I was plagued with two problems:
|
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
38221c5
to
cd1b009
Compare
@pytorchbot merge -f "Linter failure for code I did not touch" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Looks like the MyPy failure is because the the decorator |
@pytorchbot revert -m "Broke lint again" -c ignoredsignal |
@pytorchbot successfully started a revert job. Check the current status here. |
Reverting PR 92637 failedReason: Command
Details for Dev Infra teamRaised by workflow job |
#92637 broke lint, can't easily revert because of merge conflicts.
#92637 broke lint, can't easily revert because of merge conflicts. Pull Request resolved: #92759 Approved by: https://github.com/ezyang
Oof sorry about this, I've been banging into the linter like an idiot all week |
Ex output:
cc @mlazos @soumith @yanboliang @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @chunyuan-w @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @desertfire