-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Easy][Profiler] Fix pattern matcher of profiler #157711
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/157711
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 42ce8d8 with merge base c5b46b5 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 jobs have failed, first few of them are: trunk / macos-py3-arm64 / test (mps, 1, 1, macos-m2-15) Details for Dev Infra teamRaised by workflow job |
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
4fddd01
to
c9722a8
Compare
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.
@Aidyn-A do you mind adding a test before merging this?
I do not think there is any need or way of adding short unit-tests. There are already a couple of them failing if PyTorch was built with
The reason this error was not regularly observed is because of Python interrupts the >>> all(int(arch[3:]) >= 80 for arch in ['sm_70', 'sm_80', 'sm_86', 'sm_90', 'sm_100', 'sm_120', 'compute_120'])
False However, if all architectures are >=80, the Python interpreter checks the whole range and fails on >>> all(int(arch[3:]) >= 80 for arch in ['sm_80', 'sm_86', 'sm_90', 'sm_100', 'sm_120', 'compute_120'])
Traceback (most recent call last):
ValueError: invalid literal for int() with base 10: 'pute_120' |
@Aidyn-A ok sounds good. Can you fix the linter error? |
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
c9722a8
to
42ce8d8
Compare
The linter was failing due to broken CI. @pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Per title, as it fails with the following error if "+PTX" was used in
TORCH_CUDA_ARCH_LIST
:Because slicing
arch[3:]
will not end up on having only digits forcompute_120
element oftorch.cuda.get_arch_list()
:cc @ptrblck @msaroufim @eqy @jerryzh168 @robieta @chaekit @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise