Stateless tests (tsan, s3 storage) [3/5] — Tests are not finished, fail: 1

did not find anything in logs... stderr is empty, nothing in runlog, and in clickhouse-server.log only <Fatal> Application: Child process was terminated by signal 9 (KILL). If it is not done by 'forcestop' command or manually, the possible cause is OOM Killer (see 'dmesg' and look at the '/var/log/kern.log' for the details).

Stateless tests (tsan, s3 storage) [3/5] — Tests are not finished, fail: 1

did not find anything in logs... stderr is empty, nothing in runlog, and in clickhouse-server.log only <Fatal> Application: Child process was terminated by signal 9 (KILL). If it is not done by 'forcestop' command or manually, the possible cause is OOM Killer (see 'dmesg' and look at the '/var/log/kern.log' for the details).

Looks like OOM. It may be related to #44455

@nickitat, could you please take a look?

doesn't seem related. test actually didn't finished:

483769:2023.01.11 16:04:00.560851 [ 6290 ] {test_earik289_hash_table_sizes_stats_2400525607} <Trace> Aggregator: Merging aggregated data
483770:2023.01.11 16:04:00.561030 [ 6290 ] {test_earik289_hash_table_sizes_stats_2400525607} <Trace> Aggregator: Statistics updated for key=15678390843594786382: new sum_of_sizes=1000005, median_size=200001

but OOM happened 7 minutes later ...

doesn't seem related

According to the query I attached above, at the first time it failed like this in #44455 and then it started to fail in other PRs after #44455 was merged on 2023-01-09. So I'm pretty sure it's related.

test actually didn't finished

Yep, it means that OOM happened during the execution of that query (but yes, it's not clear why there are no log messages before OOM)

correlation is clear, you're right. but I don't see any reason. also it fails only under tsan as far as I see
#45287