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

Hive QA commented on HIVE-19882:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12928351/HIVE-19882.07.patch

{color:green}SUCCESS:{color} +1 due to 6 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14536 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/11948/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11948/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11948/

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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12928351 - PreCommit-HIVE-Build

> Fix QTestUtil session lifecycle
> -------------------------------
>
>                 Key: HIVE-19882
>                 URL: https://issues.apache.org/jira/browse/HIVE-19882
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Tests
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-19882.01.patch, HIVE-19882.02.patch, 
> HIVE-19882.03.patch, HIVE-19882.04.patch, HIVE-19882.05.patch, 
> HIVE-19882.06.patch, HIVE-19882.07.patch
>
>
> there are a number of strange come and go failing tests; it was always 
> strange to me that qtestutil cleans up at some questionable points - this 
> seems to be leading to executing some commands with the previous qfiles 
> session...
> ideally the session/etc should start/reused in {{before}}
> and it should be closed in {{after}}
> seems like configuration is handled probably incorrectly; saving the conf 
> after initialization - and restoring it for a new session should ensure 
> consistency



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to