[
https://issues.apache.org/jira/browse/HIVE-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971772#comment-13971772
]
Hive QA commented on HIVE-6908:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12640168/HIVE-6908.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 5401 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_auto_sortmerge_join_16
{noformat}
Test results: http://bigtop01.cloudera.org:8080/job/precommit-hive/10/testReport
Console output: http://bigtop01.cloudera.org:8080/job/precommit-hive/10/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12640168
> TestThriftBinaryCLIService.testExecuteStatementAsync has intermittent failures
> ------------------------------------------------------------------------------
>
> Key: HIVE-6908
> URL: https://issues.apache.org/jira/browse/HIVE-6908
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.13.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: HIVE-6908.patch
>
>
> This has failed sometimes in the pre-commit tests.
> ThriftCLIServiceTest.testExecuteStatementAsync runs two statements. They are
> given 100 second timeout total, not sure if its by intention. As the first
> is a select query, it will take a majority of the time. The second statement
> (create table) should be quicker, but it fails sometimes because timeout is
> already mostly used up.
> The timeout should probably be reset after the first statement. If the
> operation finishes before the timeout, it wont have any effect as it'll break
> out.
--
This message was sent by Atlassian JIRA
(v6.2#6252)