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

teuthology/scrape: Fix bad backtrace parsing in Teuthology.log #1884

Merged
merged 1 commit into from
Aug 30, 2023

Conversation

kamoltat
Copy link
Member

@kamoltat kamoltat commented Aug 17, 2023

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

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]>
@kamoltat kamoltat added the bug label Aug 17, 2023
@kamoltat kamoltat requested review from zmc and ljflores August 17, 2023 16:35
@kamoltat kamoltat self-assigned this Aug 17, 2023
Copy link
Contributor

@ljflores ljflores left a comment

Choose a reason for hiding this comment

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

Thanks!

Copy link
Member

@zmc zmc left a comment

Choose a reason for hiding this comment

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

Good catch!

@zmc
Copy link
Member

zmc commented Aug 17, 2023

The docs build failure should be addressed by sphinx-doc/sphinx#11613

@kamoltat
Copy link
Member Author

@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

@zmc
Copy link
Member

zmc commented Aug 21, 2023

@kamoltat they haven't published a release with the fix yet

@kamoltat
Copy link
Member Author

@kamoltat they haven't published a release with the fix yet

@zmc make sense, should we wait for them to publish the release? IMHO since the CI is not really labelled as required, we can just skip it?

zmc added a commit that referenced this pull request Aug 23, 2023
@zmc
Copy link
Member

zmc commented Aug 23, 2023

@kamoltat it's marked as required, but #1885 is a simple fix

@kamoltat
Copy link
Member Author

@kamoltat it's marked as required, but #1885 is a simple fix

Thanks @zmc

@kamoltat kamoltat merged commit 58348f7 into ceph:main Aug 30, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants