[ 
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742208#comment-16742208
 ] 

ASF subversion and git services commented on IMPALA-8064:
---------------------------------------------------------

Commit f8c3e4c0a44dbfa389c195c399e17a64d38a0824 in impala's branch 
refs/heads/master from Janaki Lahorani
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=f8c3e4c ]

IMPALA-8064: Fix intermittent test failures from test_min_max_filters

test_min_max_filters and test_decimal_min_max_filters records the aggregated 
probe rows to
check whether min-max filter was exercised.  In the case of ASAN builds, the 
probe side
started processing before the filters reached the probe side, because ASAN 
builds are a
little slower.  The resolution is to increase RUNTIME_FILTER_WAIT_TIME_MS to 
accommodate ASAN.

This issue was also seen earlier on a runtime filter tests and fixed through 
IMPALA-6201.  This
fix mimics the same, by setting RUNTIME_FILTER_WAIT_TIME_MS to 
$RUNTIME_FILTER_WAIT_TIME_MS.

Change-Id: I111ed15947bd2812753ae68d3bbb8a9871e25b08
Reviewed-on: http://gerrit.cloudera.org:8080/12224
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> test_min_max_filters is flaky 
> ------------------------------
>
>                 Key: IMPALA-8064
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8064
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Pooja Nilangekar
>            Assignee: Janaki Lahorani
>            Priority: Blocker
>              Labels: broken-build, flaky-test
>
> The following configuration of the test_min_max_filters:
> {code:java}
> query_test.test_runtime_filters.TestMinMaxFilters.test_min_max_filters[protocol:
>  beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0, 
> 'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 
> 'abort_on_error': 1, 'debug_action': None, 'exec_single_node_rows_threshold': 
> 0} | table_format: kudu/none]{code}
> It produces a higher aggregation of sumĀ over the proberows than expected:
> {code:java}
> query_test/test_runtime_filters.py:113: in test_min_max_filters     
> self.run_test_case('QueryTest/min_max_filters', vector) 
> common/impala_test_suite.py:518: in run_test_case     
> update_section=pytest.config.option.update_results) 
> common/test_result_verifier.py:612: in verify_runtime_profile     % 
> (function, field, expected_value, actual_value, actual)) 
> E   AssertionError: Aggregation of SUM over ProbeRows did not match expected 
> results. 
> E   EXPECTED VALUE: E   619 
> E    ACTUAL VALUE: E   652
> {code}
> This test was introduced in the patch for IMPALA-6533. The failure occurred 
> during an ASAN build. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to