[jira] [Comment Edited] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2

["Janos Makai (Jira)" <ji...@apache.org>]

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

Janos Makai edited comment on OOZIE-3675 at 11/24/22 3:09 PM:
--------------------------------------------------------------

Sure, Dénes,

Without that change we are experiencing the following exception intermittently, which causes flaky tests and sometimes failed tests:
{code:java}
Problems adding Mockito listener.
Listener of type 'MismatchReportingTestListener' has already been added and not removed.
It indicates that previous listener was not removed according to the API.
When you add a listener, don't forget to remove the listener afterwards:
  Mockito.framework().removeListener(myListener);
For more information, see the javadoc for RedundantListenerException class.
{code}
While investigating this issue, I've found we can bypass this by setting <parallel> test execution from classes to methods. According to the test runs, this eliminates the above exception.

I've now explained it in the latest patch set's commit message, and added an additional note to the pom.xml as well.

Could you please review the latest ( *OOZIE-3675-020.patch* ) patch set?


was (Author: jmakai):
Sure, Dénes,

Without that change we are experiencing the following exception intermittently, which causes flaky tests and sometimes failed tests:
{code:java}
Problems adding Mockito listener.
Listener of type 'MismatchReportingTestListener' has already been added and not removed.
It indicates that previous listener was not removed according to the API.
When you add a listener, don't forget to remove the listener afterwards:
  Mockito.framework().removeListener(myListener);
For more information, see the javadoc for RedundantListenerException class.
{code}
While investigating this issue, I've found we can bypass this by setting <parallel> test execution from classes to methods. According to the test runs, this eliminates the above exception.

I've now explained it in the latest patch set's commit message, and added an additional note to the pom.xml as well.

Could you please review the latest ( *OOZIE-3675-019.patch* ) patch set?

> Upgrade Mockito from 2 to 3.11.2
> --------------------------------
>
>                 Key: OOZIE-3675
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3675
>             Project: Oozie
>          Issue Type: Task
>    Affects Versions: 5.2.1
>            Reporter: Janos Makai
>            Assignee: Janos Makai
>            Priority: Major
>         Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, OOZIE-3675-018.patch, OOZIE-3675-019.patch, OOZIE-3675-020.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)