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

Hive QA commented on HIVE-4355:
-------------------------------



{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/12578676/HIVE-4355.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2856 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/422/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/422/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 failed with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.
                
> HCatalog test TestPigHCatUtil might fail on JDK7
> ------------------------------------------------
>
>                 Key: HIVE-4355
>                 URL: https://issues.apache.org/jira/browse/HIVE-4355
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HCatalog
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>         Attachments: HIVE-4355.patch
>
>
> I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including 
> tests) and run the tests itself on JDK 7. My motivation was to see what will 
> happen to users that will download official Apache release (usually compiled 
> on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing 
> because the order of method calls was different then when compiling and 
> running the tests only on JDK 6 or only on JDK 7.

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

Reply via email to