Skip to content

Conversation

henrylhtsang
Copy link
Contributor

@henrylhtsang henrylhtsang commented Feb 13, 2025

Copy link

pytorch-bot bot commented Feb 13, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/147061

Note: Links to docs will display an error until the docs builds have been completed.

⏳ 3 Pending, 3 Unrelated Failures

As of commit 24bfc7b with merge base b0553ce (image):

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

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

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D69573525

except NotImplementedError as e:
log.info(
"Cannot Append Choice: %s",
stack_info=True if log.getEffectiveLevel() < logging.INFO else False,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this necessary? Stack_info=True should have no effect if the level is not at least log.info level? You could also pass exc_info for a more detailed trace.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this necessary? Stack_info=True should have no effect if the level is not at least log.info level? You could also pass exc_info for a more detailed trace.

I want to print the error with a higher logging level (info) and print also the stack trace at debug so to not spam people. Let me know what you think

Copy link
Collaborator

@Skylion007 Skylion007 Feb 14, 2025

Choose a reason for hiding this comment

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

Ah I see it's, suppose to be printer at debug only. Makes sense then. Nit should probably just be a cast to bool instead of this if else

Copy link
Contributor Author

@henrylhtsang henrylhtsang Feb 14, 2025

Choose a reason for hiding this comment

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

landing with stack_info=log.getEffectiveLevel() < logging.INFO, for now. Let me know if you prefer a bool cast since it is a bit ugly right now

return None
except NotImplementedError as e:
log.info(
"Cannot Append Choice: %s",
Copy link
Collaborator

Choose a reason for hiding this comment

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

The choice % string isn't populated into this string, shouldn't it be?

@henrylhtsang henrylhtsang added the topic: not user facing topic category label Feb 13, 2025
Summary: Pull Request resolved: pytorch#147061

Differential Revision: D69573525
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D69573525

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Feb 14, 2025
@henrylhtsang
Copy link
Contributor Author

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 3 checks: inductor / unit-test / linux-jammy-cpu-py3.9-gcc11-inductor / test (inductor_amx, 2, 2, linux.8xlarge.amx), inductor / unit-test / linux-jammy-cpu-py3.9-gcc11-inductor / test (inductor_avx2, 2, 2, linux.10xlarge.avx2), trunk / win-vs2022-cuda12.1-py3 / build

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants