[
https://issues.apache.org/jira/browse/OAK-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962541#comment-15962541
]
Marcel Reutegger commented on OAK-6024:
---------------------------------------
Fixed another test in trunk: http://svn.apache.org/r1790783
> 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)
