-
Notifications
You must be signed in to change notification settings - Fork 144
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
When saving a traceback, shorten very large locals #3468
Conversation
1134196
to
b62b592
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a nitpick about the value, otherwise LGTM
b62b592
to
5e7de3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/packit test |
5e7de3f
to
769d50b
Compare
769d50b
to
1f188de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one typo, fine to ignore.
f858acd
to
791c377
Compare
A traceback in `log.txt` can be very large, especially when saving locals like a huge set of result or junit XML. Adding a level of traceback verbosity, `locals`, which will log locals, but shorten the very long ones. `full` will keep showing everything on terminal.
Co-authored-by: Petr Šplíchal <psplicha@redhat.com>
791c377
to
3d8ff5b
Compare
A traceback in
log.txt
can be very large, especially when saving locals like a huge set of result or junit XML. Adding a level of traceback verbosity,locals
, which will log locals, but shorten the very long ones.full
will keep showing everything on terminal.Pull Request Checklist