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

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

Commit 67cf0bb761688b469f9add19466475b2d6e637c2 in impala's branch 
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=67cf0bb76 ]

IMPALA-13834: Fix test_kudu_txn_abort_partition_lock.

IMPALA-10465 change execution of test_kudu_txn_abort_partition_lock. It
meant to call _test_kudu_txn_abort_partition_lock() of superclass, but
there is a copy-paste mistake that makes it call
_test_kudu_txn_abort_partial_rows() instead. This patch fix it.

Testing:
- Run and pass test_kudu_txn_abort_partition_lock.

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


> test_kudu_txn_abort_partition_lock run the wrong test method.
> -------------------------------------------------------------
>
>                 Key: IMPALA-13834
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13834
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Test
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Minor
>             Fix For: Impala 4.6.0
>
>
> IMPALA-10465 change execution of test_kudu_txn_abort_partition_lock. It meant 
> to  call _test_kudu_txn_abort_partition_lock() of superclass, but there is a 
> copy-paste mistake that makes it call _test_kudu_txn_abort_partial_rows() 
> instead.
> https://gerrit.cloudera.org/c/18536/11/tests/custom_cluster/test_kudu.py#693



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to