]> git.apps.os.sepia.ceph.com Git - teuthology.git/commit
teuthology/scrape: Fix bad backtrace parsing in Teuthology.log 1884/head
authorKamoltat Sirivadhna <ksirivad@redhat.com>
Thu, 17 Aug 2023 16:28:00 +0000 (12:28 -0400)
committerKamoltat Sirivadhna <ksirivad@redhat.com>
Thu, 17 Aug 2023 16:28:00 +0000 (12:28 -0400)
commitc4fbb219b6104c7056448a06ca1d654079bf2546
treec25a8330f04f4e37f3fc02c958e5efa650a71c1f
parent449a1bc2027504e7b3c3d7b30fa4178906581da7
teuthology/scrape: Fix bad backtrace parsing in Teuthology.log

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 <ksirivad@redhat.com>
teuthology/scrape.py