-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[profiler] add more CUDA API for kernel launcher #156016
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/156016
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 02b3c4b with merge base 655b3b1 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot label "release notes: profiler" |
torch/profiler/_utils.py
Outdated
| # TODO: find a better way to identify cudaLaunchKernel | ||
| return e.name == "cudaLaunchKernel" | ||
| """Check if the event is a CUDA launch kernel.""" | ||
| launch_patterns = [ |
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.
Nit: list should be a tuple.
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.
Thanks!
|
@pytorchbot merge |
|
Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra. |
|
@pytorchmergebot merge -f "lint is green" |
|
You are not authorized to force merges to this repository. Please use the regular |
|
@pytorchmergebot merge |
|
Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra. |
|
@albanD ; Sorry for the distraction. Could you merge this PR? |
|
@pytorchbot merge @namgyu-youn avoid force merging when no test actually ran yet ;) |
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: 2 mandatory check(s) failed. The first few are:
Dig deeper by viewing the failures on hud |
- Since `is_cuda_kernel` checks for `e.name`, it can raise an AttributeError if `e` does not have a `name` attribute. - For resolving this, we can use `hasattr` to check if `e` has a `name` attribute before accessing it.
conditioner is not needed Co-authored-by: albanD <desmaison.alban@gmail.com>
|
@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 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
@albanD It seems that GitHub Actions failed due to permission in |
|
@pytorchmergebot merge |
|
@pytorchbot merge |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
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 |
Add more kernel detection options, resolving TODO