Skip to content
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

TORCH_LOGS=dynamic equivalent in tlparse #68

Open
ezyang opened this issue Sep 25, 2024 · 2 comments
Open

TORCH_LOGS=dynamic equivalent in tlparse #68

ezyang opened this issue Sep 25, 2024 · 2 comments

Comments

@ezyang
Copy link
Contributor

ezyang commented Sep 25, 2024

In particular, knowing where guards came from is very useful. Can either build this into the guard printout (need to maintain source stack trace for guards), or can stream it out like TORCH_LOGS=dynamic and then reprint it in tlparse

@zou3519
Copy link

zou3519 commented Sep 25, 2024

@ezyang would it make sense to dump all the TORCH_LOGS we can get to tlparse?

@ezyang
Copy link
Contributor Author

ezyang commented Sep 25, 2024

Maybe info logs but because tlparse is on by default there definitely is a compile time perf hazard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants