Sema Checherinda

Stress test (msan) use-of-uninitialized-value -- https://github.com/ClickHouse/ClickHouse/issues/66525 binary_tidy -- https://github.com/ClickHouse/ClickHouse/pull/66552

At previous build: 02884_async_insert_skip_settings -- should be fixed now by https://github.com/ClickHouse/ClickHouse/pull/66771

Stateless Tests (msan) [1/4] 03203_client_benchmark_options -- it is new test and it is flaky, the fail on the master https://d1k2gkhrlfqv31.cloudfront.net/clickhouse-test-reports-private/0/51b843e4202728c65e76e3ac5546545febdf8081/stateless_tests__msan__s3_storage__[3_3].html

Stress Test (tsan) Hung check failed https://s3.amazonaws.com/clickhouse-test-reports/66279/20f22278bd4bbbf85cff4012fb12c20a03257b13/stress_test__tsan_.html This is an issue. it belongs to the test `02967_parallel_replicas_join_algo_and_analyzer.sh` initial query `09b0e14d-2a0a-4530-8620-04319e2b52fa`, dependent `6222aab4-8ac3-49cf-a9a5-4da98152593f` failed due to exception `CANNOT_SCHEDULE_TASK` second dependent `e2d5632a-116f-4070-a9fd-2556d734d34d`...

`Integration Tests Flaky Check` all tests has been fixed by Michael Stetsyuk

Hi, could you take a look, please, @justindeguzman ?

duplicate? https://github.com/ClickHouse/clickhouse-private/issues/13092 I'm working on it in https://github.com/ClickHouse/clickhouse-private/issues/13092.

Hi! I wish to discuss some points here: the volume of the logs and its value. I had in my mind the case then someone constantly with high rate are...

If exception is happened in `WriteBuffer::finalize()` then `WriteBuffer::cancel();` is called. After that d-tor is happy, it sees that instance is canceled. May be the logs come from the times before...

Do not understand your point. The cal stack looks like: `WriteBuffer::finalize()` -> `WriteBufferFromS3::finalizeImpl()` -> `WriteBufferFromS3::preFinalize()`