[
https://issues.apache.org/jira/browse/HIVE-22056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894426#comment-16894426
]
Hive QA commented on HIVE-22056:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12975981/HIVE-22056.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16710 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.beeline.TestBeeLineWithArgs.testBeelineShellCommandWithoutConn
(batchId=276)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/18180/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18180/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18180/
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
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12975981 - PreCommit-HIVE-Build
> Beeline started with -f <script-file>, exit code is 0 even if unable to
> connect to HS2
> --------------------------------------------------------------------------------------
>
> Key: HIVE-22056
> URL: https://issues.apache.org/jira/browse/HIVE-22056
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Affects Versions: 3.1.0, 4.0.0, 3.1.1
> Reporter: Himanshu Mishra
> Assignee: Himanshu Mishra
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22056.patch
>
>
> When Beeline in hive 3 is started with -f <script-file> argument, even if it
> is not able to connect to HS2 server, it exits with success code i.e. 0.
> Looks like this bug got introduced with the fix for HIVE-19744
> In previous versions it used to exit with code 2, fixing by exiting with
> same code.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
