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

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

Commit dbd454445165829541c9e2c67cce5446bb535f46 in impala's branch 
refs/heads/master from Bikramjeet Vig
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=dbd4544 ]

IMPALA-9830: Fix flakiness in test_mt_dop_scan_node

This test has inherent flakiness due to it relying on instances
fetching scan ranges from a shared queue. The time sensitivity
enhanced the flakiness on a release build. So this change decreases
the mt_dop level to 8 which results in a failure rate of 0.05%.
This along with increasing the num of tries should make sure flakiness
is removed.

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


> TestMtDopScanNode.test_mt_dop_scan_node fails BytesRead > 0 assert
> ------------------------------------------------------------------
>
>                 Key: IMPALA-9830
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9830
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.0
>            Reporter: Joe McDonnell
>            Assignee: Bikramjeet Vig
>            Priority: Blocker
>              Labels: broken-build, flaky
>
> A few test runs have seen this failure in 
> TestMtDopScanNode.test_mt_dop_scan_node():
> {noformat}
> query_test/test_mt_dop.py:134: in test_mt_dop_scan_node
>     assert "- BytesRead: 0" not in result.runtime_profile, 
> result.runtime_profile{noformat}
> This test is run in a loop due to IMPALA-9655. We may need to increase the 
> number of loops or rethink the conditions of the test.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to