log if maxMem is called twice in a task#13454
Merged
Merged
Conversation
Signed-off-by: Zach Puller <zpuller@nvidia.com>
sameerz
added
the
task
Collaborator
Author
|
build |
jihoonson
approved these changes
Sep 29, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
This change adds an error log line for if
GpuTaskMetrics.updateMaxMemorygets called more than once for a given task. This will help to debug #13336Checklists
No behavioral change.
(Please explain in the PR description how the new code paths are tested, such as names of the new/existing tests that cover them.)