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

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

Commit 43121bac7d94d17e79720363cea309211fad74be in impala's branch 
refs/heads/master from [~fredyw]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=43121ba ]

IMPALA-7794: Rewrite flaky ownership authorization tests

This patch rewrites the ownership authorization tests to not depend on
delay and timeout, which can help to avoid the flakiness. The patch also
refactors some tests to reuse Sentry and Impala instances without having
to restart them, which can speed up the tests. To keep the same test
coverage, no tests were removed.

Testing:
- Ran all authorization E2E tests multiple times.

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


> Rewrite ownership authorization tests
> -------------------------------------
>
>                 Key: IMPALA-7794
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7794
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.1.0
>            Reporter: Fredy Wijaya
>            Assignee: Fredy Wijaya
>            Priority: Critical
>             Fix For: Impala 3.1.0
>
>
> The ownership tests have been very flaky. There were few attempts to fix 
> them, but none of them have truly fixed the flakiness due to the tests are 
> timing-based. Some of the tests are also not very readable. Those tests need 
> to be rewritten while keeping the code coverage.



--
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