[
https://issues.apache.org/jira/browse/IGNITE-26591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Chesnokov updated IGNITE-26591:
-----------------------------------------
Description:
PerformanceStatisticsThinClientTest#testCompute with
[atomicityMode=ATOMIC]fails at PerformanceStatisticsThinClientTest.java:162
{noformat}
assertTrue(taskStartTime >= startTime);{noformat}
The difference between taskStartTime and startTime can be about 100millis
It looks like using U.currentTimeMillis() can give some time inaccuracy
was:
PerformanceStatisticsThinClientTest#testCompute with
[atomicityMode=ATOMIC]fails at PerformanceStatisticsThinClientTest.java:162
{noformat}
assertTrue(taskStartTime >= startTime);{noformat}
The difference between taskStartTime and startTime can be about 100millis
It looks like using U.currentTimeMillis() can give some time с
> PerformanceStatisticsThinClientTest#testCompute fails
> -----------------------------------------------------
>
> Key: IGNITE-26591
> URL: https://issues.apache.org/jira/browse/IGNITE-26591
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Chesnokov
> Priority: Major
> Labels: IEP-35
>
> PerformanceStatisticsThinClientTest#testCompute with
> [atomicityMode=ATOMIC]fails at PerformanceStatisticsThinClientTest.java:162
>
> {noformat}
> assertTrue(taskStartTime >= startTime);{noformat}
> The difference between taskStartTime and startTime can be about 100millis
> It looks like using U.currentTimeMillis() can give some time inaccuracy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
