Alexey MilovidovandClaude Opus 4.6 f7722f1884 Wait for server ports to be freed before starting a new instance ...

After `safeExit` (forceful shutdown due to stuck client connections),
the kernel may still be cleaning up sockets, especially under sanitizer
builds where `SYS_exit_group` is used. The `safeExit` path skips the
normal `SCOPE_EXIT_SAFE` handler that closes interserver (9009) and
Keeper (9181) listening sockets, leaving them to kernel cleanup which
can race with the next server start.

Add `wait_server_port_free` to check port availability before starting,
so `start_server` waits for ports 9000, 9009, and 9181 to be released.

CI report: https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=98454&sha=48200cc58dec962ea1624acc23da4372e73fa52c&name_0=PR&name_1=Stress%20test%20%28amd_tsan%29

Co-Authored-By: Claude Opus 4.6 <[email protected]>

2026-03-02 19:29:51 +01:00

..

attach_gdb.lib

…

create.sql

…

stress_runner.sh

Revert "ci: fix fast limits"

2026-02-26 07:08:38 +01:00

stress_tests.lib

Wait for server ports to be freed before starting a new instance

2026-03-02 19:29:51 +01:00

upgrade_runner.sh

Suppress Key expressions cannot contain subqueries error in upgrade check

2026-02-19 21:44:39 +01:00

utils.lib

…