[IMPALA-9185] TestBloomFilters.test_bloom_wait_time is flaky on S3

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Labels: broken-build flaky
• Epic Color: ghx-label-5
• Assignee: Unassigned
• Reporter: Sahil Takiar
• Created: 22/Nov/19 05:06
• Updated: 06/Aug/20 23:22
• Resolved: 06/Aug/20 23:22

Description

The following test is flaky on S3, we should consider increasing the arrival timeout; similar to what was done on ASAN builds in IMPALA-7104

query_test.test_runtime_filters.TestBloomFilters.test_bloom_wait_time[protocol: beeswax | exec_option: \{'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format: rc/snap/block] (from pytest)

Error Message

query_test/test_runtime_filters.py:135: in test_bloom_wait_time assert duration_s < (WAIT_TIME_MS / 1000), \ E AssertionError: Query took too long (200.51018095s, possibly waiting for missing filters?) E assert 200.5101809501648 < (60000 / 1000)

Stacktrace

query_test/test_runtime_filters.py:135: in test_bloom_wait_time assert duration_s < (WAIT_TIME_MS / 1000), \ E AssertionError: Query took too long (200.51018095s, possibly waiting for missing filters?) E assert 200.5101809501648 < (60000 / 1000)

Issue Links

• is related to: IMPALA-7104 test_bloom_wait_time failing with timeout on asan
• is related to: IMPALA-6998 test_bloom_wait_time fails due to late arrival of filters on Isilon