[
https://issues.apache.org/jira/browse/IGNITE-23117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880211#comment-17880211
]
Vladislav Pyatkov commented on IGNITE-23117:
--------------------------------------------
I ran the patch 8 times, and it failed in two tests from all runs.
Both fails are not connected with this chage. Therefore, I am sure this PR is
ready for review.
> Substitute systemUTC with currentTimeMillis in HybridClockImpl
> --------------------------------------------------------------
>
> Key: IGNITE-23117
> URL: https://issues.apache.org/jira/browse/IGNITE-23117
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Alexander Lapin
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> For more details please see https://issues.apache.org/jira/browse/IGNITE-23049
> h3. Definition of Done
> * It's required to substitute current
> org.apache.ignite.internal.hlc.HybridClockImpl#currentTime
> {code:java}
> private static long currentTime() {
> return systemUTC().instant().toEpochMilli() << LOGICAL_TIME_BITS_SIZE;
> }{code}
> with
> {code:java}
> private static long currentTime() {
> return System.currentTimeMillis() << LOGICAL_TIME_BITS_SIZE;
> }{code}
> * And adjust mocks in HybridClockTest.
> * And of course ensure that currentTimeMillis based implementation is stable
> by multiple TC runs.
> h3. Implementation Notes
> The only non-trivial part here is mock adjustments in the test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
