[
https://issues.apache.org/jira/browse/HIVE-29237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zsolt Miskolczi updated HIVE-29237:
-----------------------------------
Description:
TestHiveCommitLocks is flaky on downstream. I couldn't reproduce the issue on
upstream but I'm pretty sure it can happen any time - as the test cases are
reusing resources.
Update:
With the help of [~dkuzmenko] , the root cause is identified:
It seems Hive: Refactor commit lock mechanism from HiveTableOperations (#6648)
port from Iceberg had a mistake and left two
doNothing().when(spyOps).doUnlock(any()); calls in the test class.
was:
TestHiveCommitLocks is flaky on downstream. I couldn't reproduce the issue on
upstream but I'm pretty sure it can happen any time - as the test cases are
reusing resources.
> TestHiveCommitLocks flakyness
> -----------------------------
>
> Key: HIVE-29237
> URL: https://issues.apache.org/jira/browse/HIVE-29237
> Project: Hive
> Issue Type: Task
> Reporter: Zsolt Miskolczi
> Assignee: Zsolt Miskolczi
> Priority: Major
> Labels: pull-request-available
>
> TestHiveCommitLocks is flaky on downstream. I couldn't reproduce the issue on
> upstream but I'm pretty sure it can happen any time - as the test cases are
> reusing resources.
> Update:
> With the help of [~dkuzmenko] , the root cause is identified:
> It seems Hive: Refactor commit lock mechanism from HiveTableOperations
> (#6648) port from Iceberg had a mistake and left two
> doNothing().when(spyOps).doUnlock(any()); calls in the test class.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
