Michał Chojnowski df93ea626b test/scylla_gdb: use gcore instead of signal SIGSEGV to generate a coredump on failure ...

The test fails in CI sometimes, and we want a coredump from a failure
to debug that. We made the test send a `signal SIGSEGV` to Scylla
on failure, but apparently that doesn't work as intended on our CI
hosts. (The CI runner seemingly can't find any coredump afterwards).

We can use gdb's `gcore` command to produce a coredump in a more
predictable way.

Refs scylladb/scylladb#22501

Closes scylladb/scylladb#27498

2025-12-16 06:53:43 +02:00

..

__init__.py

test.py: Create central conftest.

2024-11-24 20:09:48 +02:00

conftest.py

test/scylla_gdb: better error message when running on dev build mode

2025-04-22 15:02:06 +03:00

run

test.py: modify run to use different junit output filenames

2025-09-01 08:56:48 +03:00

suite.yaml

test/scylla_gdb: get table::_schema raw pointer with lw_shared_ptr

2024-09-22 18:30:16 +03:00

test_misc.py

test/scylla_gdb: use gcore instead of signal SIGSEGV to generate a coredump on failure

2025-12-16 06:53:43 +02:00