[
https://issues.apache.org/jira/browse/HIVE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719087#comment-16719087
]
Hive QA commented on HIVE-21022:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12951497/HIVE-21022.04
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15615 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/15279/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/15279/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-15279/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12951497 - PreCommit-HIVE-Build
> Fix remote metastore tests which use ZooKeeper
> ----------------------------------------------
>
> Key: HIVE-21022
> URL: https://issues.apache.org/jira/browse/HIVE-21022
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 4.0.0
> Reporter: Ashutosh Bapat
> Assignee: Ashutosh Bapat
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21022.01, HIVE-21022.01, HIVE-21022.01,
> HIVE-21022.02, HIVE-21022.02.patch, HIVE-21022.03, HIVE-21022.03,
> HIVE-21022.04
>
>
> Per [~vgarg]'s comment on HIVE-20794 at
> https://issues.apache.org/jira/browse/HIVE-20794?focusedCommentId=16714093&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16714093,
> the remote metatstore tests using ZooKeeper are flaky. They are failing with
> error "Got exception: org.apache.zookeeper.KeeperException$NoNodeException
> KeeperErrorCode = NoNode for /hs2mszktest".
> Both of these tests are using the same root namespace and hence the reason
> for this failure could be that the root namespace becomes unavailable to one
> test when the other drops it. The drop seems to be happening automatically
> through TestingServer code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
