-
Notifications
You must be signed in to change notification settings - Fork 290
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
teuthology/scrape: Fix bad backtrace parsing in Teuthology.log #1884
Conversation
Problem: - confusing warning message stating that the back trace is malformed - We kept adding to the backtrace buffer even when we exceeded the `MAX_BT_LINES` Solution: - Correct the warning message to be "Ignoring backtrace that exceeds MAX_BT_LINES" - reset the buffer once we exceeded MAX_BT_LINES - Added some cases where we detect start/end of back trace. Fixes:https://tracker.ceph.com/issues/62445 Signed-off-by: Kamoltat Sirivadhna <[email protected]>
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.
Thanks!
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.
Good catch!
The docs build failure should be addressed by sphinx-doc/sphinx#11613 |
@zmc Thanks for filing the PR to fix the sphinx issue :) I tried re-running the CI again after sphinx-doc/sphinx#11613 was merged, but it seems to still be failing with the same error :( I wonder if I need to do something more to get the latest update of the patch in my CI |
@kamoltat they haven't published a release with the fix yet |
See #1884 Signed-off-by: Zack Cerza <[email protected]>
Problem:
confusing warning message stating that the back trace is malformed
We kept adding to the backtrace buffer even when we exceeded the
MAX_BT_LINES
Solution:
Fixes: https://tracker.ceph.com/issues/62445