[
https://issues.apache.org/jira/browse/HIVE-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923480#comment-15923480
]
Hive QA commented on HIVE-16192:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12858566/HIVE-16192.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10339 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestSparkNegativeCliDriver.org.apache.hadoop.hive.cli.TestSparkNegativeCliDriver
(batchId=232)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4113/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4113/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4113/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 12858566 - PreCommit-HIVE-Build
> QTestUtil doesn't correctly set the last command when running "test" commands
> ------------------------------------------------------------------------------
>
> Key: HIVE-16192
> URL: https://issues.apache.org/jira/browse/HIVE-16192
> Project: Hive
> Issue Type: Bug
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Attachments: HIVE-16192.patch
>
>
> {{QTestUtil}} has some logic to execute "test" commands, these are typically
> "crypto" commands. These "test" commands, aren't valid HiveQL, but can be run
> in qtests.
> The "crypto" commands are used to setup encryption keys and zones for the
> {{TestEncryptedHDFSCliDriver}}
> When debugging HIVE-15991 I noticed that the command printed out in
> {{QTestUtil.failed}} is incorrect. It's printing out the last Hive command
> run, even if a more recent "test" command has been run. This can be very
> misleading when debugging qtest failures.
> The attached patch updates the {{QTestUtil.executeTestCommand}} method so
> that is correctly sets the last executed "test" command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)