ChangelogBackendTestCase.java:
Hopefully say forever goodbye to randomness of searchInChangeNumberModeOnOneSuffixMultipleTimes().

The fixxed assertion error message was:
Failure Cause: java.lang.AssertionError: [In entry dn:
firstchangenumber: 1
lastchangenumber: 8
changelog: cn=changelog
lastExternalChangelogCookie: o=test:00000149a520c3ed04b10000000a;
incorrect value for attr 'lastchangenumber']
Expecting:
<"8">
to be equal to:
<"9">
ignoring case considerations
org.opends.server.backends.ChangelogBackendTestCase.assertAttributeValue(ChangelogBackendTestCase.java:1381)
org.opends.server.backends.ChangelogBackendTestCase.assertChangelogAttributesInRootDSE(ChangelogBackendTestCase.java:857)
org.opends.server.backends.ChangelogBackendTestCase.searchInChangeNumberModeOnOneSuffixMultipleTimes(ChangelogBackendTestCase.java:588)


The error was due to the CSN of the 9nth change coming after the previous CSN, based on time.
How is that possible? I have absolutely no idea since both were created by using which should never go backwards AFAIK.