[jira] [Updated] (OAK-12218) reset ClusterNodeInfo clock in UnrecoveredRevisionTest tearDown to avoid CI flakiness

["Rishabh Daim (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-12218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rishabh Daim updated OAK-12218:
-------------------------------
    Description: 
_UnrecoveredRevisionTest_ sets a virtual clock in setup _(ClusterNodeInfo.setClock(virtualClock))_ and currently does not reset it in {_}tearDown(){_}.
This leaks static clock state to subsequent tests in the same JVM and causes order-dependent failures.

 

This has caused downstream failure in _DocumentDiscoveryLiteServiceIT.testLargeStartStopFiesta_

  was:
_DocumentNodeStoreIT_ sets a virtual clock via _ClusterNodeInfo.setClock(clock)_ in _doUnmergedCommitOnRoot(...)_ but does not reset the static clock afterward.

Because _ClusterNodeInfo.clock_ is JVM-static, later tests in the same Surefire fork inherit this virtual clock and can fail nondeterministically.

This has caused downstream failure in _DocumentDiscoveryLiteServiceIT.testLargeStartStopFiesta_


> reset ClusterNodeInfo clock in UnrecoveredRevisionTest tearDown to avoid CI flakiness
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-12218
>                 URL: https://issues.apache.org/jira/browse/OAK-12218
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Rishabh Daim
>            Assignee: Rishabh Daim
>            Priority: Major
>
> _UnrecoveredRevisionTest_ sets a virtual clock in setup _(ClusterNodeInfo.setClock(virtualClock))_ and currently does not reset it in {_}tearDown(){_}.
> This leaks static clock state to subsequent tests in the same JVM and causes order-dependent failures.
>  
> This has caused downstream failure in _DocumentDiscoveryLiteServiceIT.testLargeStartStopFiesta_



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