Kamil Braun

> It was reported that topology tests don't run in debug mode. Most of them do.

topology_custom/suite.yaml: ``` skip_in_debug: - test_shutdown_hang - test_replace - test_old_ip_notification_repro - test_node_shutdown_waits_for_pending_requests ``` + topology_experimental_raft/suite.yaml: ``` skip_in_debug: - test_cdc_generation_clearing - test_cdc_generation_publishing ``` + ```python3 @skip_mode('debug', 'aarch64/debug is unpredictably slow', platform_key='aarch64') async...

- `test_shutdown_hang` is a regression test to reproduce very specific issue -- it reproduced outside debug, so no point running it in debug - same for `test_old_ip_notification_repro` - same for...

Let's also use this opportunity to migrate from `skip_in_*` to `@skip_mode`

> if there is a write failure when trying to write the request data to the socket, read(0 bytes) from the socket, to see if there is an EOF. If...

> The most problems we have in tests is because the driver is sometimes closing connections for no apparent reason Example of this behavior: https://github.com/scylladb/python-driver/issues/317

The root cause of the failure -- scenario leading to a missing mapping -- is not a recent regression. But the fact that it now causes `on_internal_error` failure is a...

Also @margdoc please write down an explanation how we end up with an entry in `locator::topology` that does not have an IP. (With some pointers to code)

On one hand the scenario presented looks like it's hard to hit -- we need a crash in very specific moment. On the other, because of the recently introduced `on_internal_error`,...

Moving the release blocker label to https://github.com/scylladb/scylladb/issues/18843