You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/05/30 08:39:15 UTC

[jira] [Closed] (OAK-6024) Use of DocumentMKBuilderProvider with virtual clock is fragile

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

Davide Giannella closed OAK-6024.
---------------------------------

Bulk close for 1.7.0

> Use of DocumentMKBuilderProvider with virtual clock is fragile
> --------------------------------------------------------------
>
>                 Key: OAK-6024
>                 URL: https://issues.apache.org/jira/browse/OAK-6024
>             Project: Jackrabbit Oak
>          Issue Type: Test
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.7.0, 1.8
>
>
> Using a DocumentMKBuilderProvider rule in a test with a virtual clock is fragile, because many tests reset the clock in Revision and ClusterNodeInfo in a {{@After}} method. This may cause problems because the {{@After}} method is called before the builder provider's {{after()}} method. Between those two calls a DocumentNodeStore instance may be running with a reset clock, while it was initialied with a virtual clock.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)