[
https://issues.apache.org/jira/browse/OOZIE-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644874#comment-17644874
]
Janos Makai commented on OOZIE-3685:
------------------------------------
Sure, Dénes.
During my investigation, I've found that if we use the queue() method for
launching callables, then we do not have much control over the execution and
outcome of them, and it could be different on different machines so it's safe
to say that it's not deterministic.
However, queueSerial() can be used instead in order to achieve deterministic
outcome, which then leads to eliminating the flakiness of the test.
Furthermore, I've made several testing locally to prove this.
I hope this helped you to understand the nature of this issue and feel free to
ask if something is not clear.
> Repair flaky testCoordActionInputCheckXCommandUniqueness unit test
> ------------------------------------------------------------------
>
> Key: OOZIE-3685
> URL: https://issues.apache.org/jira/browse/OOZIE-3685
> Project: Oozie
> Issue Type: Bug
> Reporter: Janos Makai
> Assignee: Janos Makai
> Priority: Major
> Attachments: OOZIE-3685-001.patch
>
>
> org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> unit test is flaky.
> This unit test failure can be reproduced easily using the following command:
> {code:java}
> mvn clean package test
> -Dtest=org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> {code}
> The goal of this Jira is to eliminate this intermittent behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
