Skip to content

Conversation

@scylladbbot
Copy link

Current logic for decoding backtrace was locking db log processing for duration of getting path to scylla debug file. Also it was downloading debug file once - possibly resulting in wrong backtrace decode in upgrade tests.

Moved logic for getting debug file info to decoding queue, so it's not locking db log processing loop. Also downloading debug file to monitor node (where decoding is done) to /tmp/debug_<build_id> and skipping download if it's already there.

closes: https://github.com/scylladb/qa-tasks/issues/57

Testing

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)

  • Add unit tests to cover my changes (under unit-test/ folder)

  • Update the Readme/doc folder relevant to this change (if needed)

  • (cherry picked from commit 7bf36b3)

Parent PR: #10646

Current logic for decoding backtrace was locking db log processing for
duration of getting path to scylla debug file. Also it was downloading
debug file once - possibly resulting in wrong backtrace decode in upgrade
tests.

Moved logic for getting debug file info to decoding queue, so it's not
locking db log processing loop. Also downloading debug file to monitor
node (where decoding is done) to `/tmp/debug_<build_id>` and skipping
download if it's already there.

closes: https://github.com/scylladb/qa-tasks/issues/57
(cherry picked from commit 7bf36b3)
@soyacz soyacz merged commit 3697c8a into scylladb:branch-2024.2 Apr 29, 2025
6 checks passed
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

Successfully merging this pull request may close these issues.

2 participants