[OAK-10562] document-store: improve control over custom clocks set by tests

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: documentmk, test
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 23/Nov/23 16:37
• Updated: 23/Nov/23 16:37

Description

We currently allow tests to provide custom clocks for Revision and ClusterNodeInfo.

This is problematic if they are reset properly at the end of a test, because then other tests can start to behave strangely.

Proposal: refuse to set a custom clock when one is already set, and report where is was set.