drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arina Ielchiieva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5383) Several impersonation unit tests fail in unit test
Date Wed, 18 Oct 2017 15:31:00 GMT

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

Arina Ielchiieva commented on DRILL-5383:
-----------------------------------------

Well, I guess you need to provide more details before we decide to ignore these tests or not
since issue seems to be reproducible on your environment...

> Several impersonation unit tests fail in unit test
> --------------------------------------------------
>
>                 Key: DRILL-5383
>                 URL: https://issues.apache.org/jira/browse/DRILL-5383
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Chunhui Shi
>            Priority: Critical
>
> Run several round unit tests and got these errors:
> Failed tests: 
>   TestInboundImpersonationPrivileges.twoTargetGroups:135->run:62 proxyName: user3_2
targetName: user4_2 expected:<true> but was:<false>
>   TestInboundImpersonationPrivileges.oneTargetGroup:118->run:62 proxyName: user5_1
targetName: user4_2 expected:<true> but was:<false>
>   TestInboundImpersonationPrivileges.twoTargetUsers:126->run:62 proxyName: user5_2
targetName: user0_2 expected:<true> but was:<false>
> Tests in error: 
>   TestDrillbitResilience.memoryLeaksWhenCancelled:890->assertCancelledWithoutException:532
» 
>   TestInboundImpersonation.selectChainedView:136 »  org.apache.drill.common.exce...
>   TestImpersonationQueries.org.apache.drill.exec.impersonation.TestImpersonationQueries
» UserRemote
> Notice that if I run unit test in my setup, which has different settings.xml for maven
to point to our internal repository I often (maybe 1 out of 2 runs) got different error at
TestOptionsAuthEnabled#updateSysOptAsUserInAdminGroup, 
> Since the error is quite consistent when the unit test is built on different nodes. I
guess when we introduce more jars(kerby?) for unit tests we may not do the exclusion enough
so conflicts are different for different builds.
> We should be able to find out why it failed by remote debugging into these particular
tests.
> If we could not address this issue in one or two days, this JIRA should be used to disable
these tests for now. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message