[
https://issues.apache.org/jira/browse/HIVE-23233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086128#comment-17086128
]
Hive QA commented on HIVE-23233:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13000253/HIVE-23233.2.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17130 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/21730/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21730/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21730/
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: 13000253 - PreCommit-HIVE-Build
> Using default operation logs location cause hive service session testing
> failed
> -------------------------------------------------------------------------------
>
> Key: HIVE-23233
> URL: https://issues.apache.org/jira/browse/HIVE-23233
> Project: Hive
> Issue Type: Bug
> Reporter: RuiChen
> Assignee: RuiChen
> Priority: Minor
> Attachments: HIVE-23233.1.patch, HIVE-23233.2.patch
>
>
> TestSessionCleanup and TestSessionManagerMetrics tests apply the default
> operation logs location
> "ConfVars.*HIVE_SERVER2_LOGGING_OPERATION_LOG_LOCATION*", it's same OS path,
> in TestSessionManagerMetrics SessionManager will delete the operation logs
> directory on testing exit, and in TestSessionCleanup the file count will be
> checked in operation logs directory, so if these test cases are executed in
> parrallel, they will impact each other.
> I run Hive tests in my local machine and enable maven parallel mode to run
> tests with option "-T 4 -DforkCount=4", it will run test class in separeted
> processes and execute test class in parallel, you can try to run tests
> several times, this issue should happen.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)