fix: updating ucxx, which appears to avoid occasional segfaults when profiling #3420
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ling Signed-off-by: jdebache <[email protected]>
|
/bot run |
|
PR_Github #1619 [ run ] triggered by Bot |
Shixiaowei02
approved these changes
Apr 9, 2025
|
what error you encounter? |
|
PR_Github #1619 [ run ] completed with state |
|
@chuangz0, waiting for your review to merge. |
chuangz0
approved these changes
Apr 10, 2025
|
/bot reuse-pipeline |
|
PR_Github #1769 [ reuse-pipeline ] triggered by Bot |
|
PR_Github #1769 [ reuse-pipeline ] completed with state |
Superjomn
pushed a commit
to Superjomn/TensorRT-LLM
that referenced
this pull request
Apr 11, 2025
…profiling (NVIDIA#3420) Signed-off-by: jdebache <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I observed some segfaults and other strange behaviour when running nsys profile on the application recently. The stack was referring to this dependency. I tried updating it, it appears to have solved the issue.