You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Taras Bobrovytsky (JIRA)" <ji...@apache.org> on 2017/08/03 17:41:01 UTC
[jira] [Created] (IMPALA-5761) Flaky test:
TestRowsAvailability::test_rows_availability
Taras Bobrovytsky created IMPALA-5761:
-----------------------------------------
Summary: Flaky test: TestRowsAvailability::test_rows_availability
Key: IMPALA-5761
URL: https://issues.apache.org/jira/browse/IMPALA-5761
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 2.10.0
Reporter: Taras Bobrovytsky
There was a random failure in one of our builds of the TestRowsAvailability test.
Here's what the error looks like:
{code}
TestRowsAvailability.test_rows_availability[query: select * from functional.alltypestiny where month = 1 and bool_col = sleep(1000) | 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: text/none]
query_test/test_rows_availability.py:84: in test_rows_availability
assert rows_avail_ms >= self.ROWS_AVAIL_LOWER_BOUND_MS,\
E AssertionError: The 'Rows available' timeline event was marked prematurely 1844ms after the previous timeline event.
E Expected the event to be marked no earlier than 2000ms after the previous event.
E Query: select * from functional.alltypestiny where month = 1 and bool_col = sleep(1000)
E assert 1844 >= 2000
E + where 2000 = <test_rows_availability.TestRowsAvailability object at 0x7fafcb526c10>.ROWS_AVAIL_LOWER_BOUND_MS
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)