KEMBAR78
[profiler] add more CUDA API for kernel launcher by namgyu-youn · Pull Request #156016 · pytorch/pytorch · GitHub
Skip to content

Conversation

@namgyu-youn
Copy link
Contributor

Add more kernel detection options, resolving TODO

@namgyu-youn namgyu-youn requested a review from sraikund16 as a code owner June 15, 2025 10:17
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 15, 2025

🔗 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 Failures

As of commit 02b3c4b with merge base 655b3b1 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@namgyu-youn
Copy link
Contributor Author

@pytorchbot label "release notes: profiler"

@pytorch-bot pytorch-bot bot added the release notes: profiler release notes category label Jun 15, 2025
# TODO: find a better way to identify cudaLaunchKernel
return e.name == "cudaLaunchKernel"
"""Check if the event is a CUDA launch kernel."""
launch_patterns = [
Copy link
Collaborator

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.

@namgyu-youn namgyu-youn changed the title add more CUDA API for kernel launcher [profiler] add more CUDA API for kernel launcher Jun 17, 2025
@namgyu-youn namgyu-youn requested a review from Skylion007 June 17, 2025 06:18
@colesbury colesbury requested a review from albanD June 17, 2025 12:25
@colesbury colesbury added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 17, 2025
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@namgyu-youn
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 24, 2025

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.

@namgyu-youn
Copy link
Contributor Author

@pytorchmergebot merge -f "lint is green"

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 24, 2025

You are not authorized to force merges to this repository. Please use the regular @pytorchmergebot merge command instead

@namgyu-youn
Copy link
Contributor Author

@pytorchmergebot merge

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 24, 2025

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.

@namgyu-youn
Copy link
Contributor Author

@albanD ; Sorry for the distraction. Could you merge this PR?

@albanD
Copy link
Collaborator

albanD commented Jun 24, 2025

@pytorchbot merge

@namgyu-youn avoid force merging when no test actually ran yet ;)

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 24, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 2 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

- 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.
@pytorch-bot pytorch-bot bot removed the ciflow/trunk Trigger trunk jobs on your pull request label Jun 24, 2025
@namgyu-youn namgyu-youn requested a review from albanD June 24, 2025 18:42
conditioner is not needed

Co-authored-by: albanD <desmaison.alban@gmail.com>
@namgyu-youn namgyu-youn requested a review from albanD June 26, 2025 03:17
@albanD
Copy link
Collaborator

albanD commented Jun 26, 2025

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 26, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@namgyu-youn
Copy link
Contributor Author

namgyu-youn commented Jun 27, 2025

@albanD It seems that GitHub Actions failed due to permission in sudo (following), but I am not certain about the reason. Could you lead me for resolving this?

+ echo '    sudo: setrlimit(RLIMIT_STACK): Operation not permitted'
    sudo: setrlimit(RLIMIT_STACK): Operation not permitted
+ echo 'For more details refer to https://github.com/sudo-project/sudo/issues/42'
For more details refer to https://github.com/sudo-project/sudo/issues/42
+ sudo chown -R 1000 /var/lib/jenkins/workspace
Error: Process completed with exit code 22.

@namgyu-youn
Copy link
Contributor Author

@pytorchmergebot merge

@namgyu-youn
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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
For more information see pytorch-bot wiki.

@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@namgyu-youn namgyu-youn deleted the profiler_refactor branch July 3, 2025 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged open source release notes: profiler release notes category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants