[
https://issues.apache.org/jira/browse/HIVE-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713085#comment-13713085
]
Hive QA commented on HIVE-4883:
-------------------------------
{color:red}Overall{color}: -1 build exited with an error
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12593068/HIVE-4883.02.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s)
Failed tests:
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_bucketizedhiveinputformat
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/82/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/82/console
Messages:
Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
This message is automatically generated.
> TestHadoop20SAuthBridge tests fail sometimes because of race condition
> ----------------------------------------------------------------------
>
> Key: HIVE-4883
> URL: https://issues.apache.org/jira/browse/HIVE-4883
> Project: Hive
> Issue Type: Bug
> Components: Metastore, Tests
> Affects Versions: 0.11.0
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Attachments: HIVE-4883.01.patch, HIVE-4883.02.patch,
> HIVE-4883.patch.dependson-HIVE-3255, HIVE-4883-reproduce.patch
>
>
> TestHadoop20SAuthBridge tests testSaslWithHiveMetaStore and
> testMetastoreProxyUser sometimes fail. I have seen this more often on mac and
> windows, but this can happen on linux as well.
> The problem is that metastore is started in a different thread and these unit
> tests actually rely on the metastore having initialized
> DelegationTokenSecretManager in HadoopThriftAuthBridge20S as part of the
> metastore startup (HiveMetaStore.startMetaStore )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
