Flaky test 03172_error_log_table_not_empty #65601
Description
03172_error_log_table_not_empty is flaky: https://s3.amazonaws.com/clickhouse-test-reports/65562/7bbd14cd5e85f19ab67febe44b1d4c4203d3ed3a/stateless_tests__debug__s3_storage__[3_6].html
It happened a few times since it was introduced:
Seems when the test takes longer than 60s the output is as follows:
2024-06-23 16:28:01 --- /usr/share/clickhouse-test/queries/0_stateless/03172_error_log_table_not_empty.reference 2024-06-23 15:56:44.204057791 -0400
2024-06-23 16:28:01 +++ /tmp/clickhouse-test/0_stateless/03172_error_log_table_not_empty.stdout 2024-06-23 16:28:01.422424742 -0400
2024-06-23 16:28:01 @@ -1,6 +1,6 @@
2024-06-23 16:28:01 1
2024-06-23 16:28:01 1
2024-06-23 16:28:01 1
2024-06-23 16:28:01 -1
2024-06-23 16:28:01 -1
2024-06-23 16:28:01 -1
2024-06-23 16:28:01 +0
2024-06-23 16:28:01 +0
2024-06-23 16:28:01 +0
2024-06-23 16:28:01
2024-06-23 16:28:01
2024-06-23 16:28:01
2024-06-23 16:28:01 MergeTree settings used in test: --ratio_of_defaults_for_sparse_serialization 1.0 --prefer_fetch_merged_part_size_threshold 10737418240 --vertical_merge_algorithm_min_rows_to_activate 161045 --vertical_merge_algorithm_min_columns_to_activate 1 --allow_vertical_merges_from_compact_to_wide_parts 0 --min_merge_bytes_to_use_direct_io 10737418240 --index_granularity_bytes 19059251 --merge_max_block_size 10957 --index_granularity 55885 --min_bytes_for_wide_part 0 --marks_compress_block_size 55051 --primary_key_compress_block_size 35835 --replace_long_file_name_to_hash 0 --max_file_name_length 128 --min_bytes_for_full_part_storage 107687786 --compact_parts_max_bytes_to_buffer 322963700 --compact_parts_max_granules_to_buffer 92 --compact_parts_merge_max_bytes_to_prefetch_part 14770024 --cache_populated_by_fetch 1 --concurrent_part_removal_threshold 100 --old_parts_lifetime 207
2024-06-23 16:28:01
2024-06-23 16:28:01 Database: test_uox7lned
Seems that the 2nd part of the test that ensures that if there are errors after the first ones happened are not taken into account properly.
However, there is another case in which the test is executed fast but the result is wrong as well:
2024-06-18 18:08:53 --- /ClickHouse/tests/queries/0_stateless/03172_error_log_table_not_empty.reference 2024-06-18 18:03:11.821186847 +0200
2024-06-18 18:08:53 +++ /ClickHouse/tests/queries/0_stateless/03172_error_log_table_not_empty.stdout 2024-06-18 18:08:53.688805575 +0200
2024-06-18 18:08:53 @@ -1,6 +1,6 @@
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 -1
2024-06-18 18:08:53 +0
2024-06-18 18:08:53 +0
2024-06-18 18:08:53 +0
2024-06-18 18:08:53 +0
2024-06-18 18:08:53 +0
2024-06-18 18:08:53 +0
2024-06-18 18:08:53
2024-06-18 18:08:53
2024-06-18 18:08:53
2024-06-18 18:08:53 Database: test_5qzbu8tt