[
https://issues.apache.org/jira/browse/IGNITE-21475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815882#comment-17815882
]
Ignite TC Bot commented on IGNITE-21475:
----------------------------------------
{panel:title=Branch: [pull/11239/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 4{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7740118]]
* IgnitePdsTestSuite4:
IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testActivateReadOnlyCachesRestore_SingleNode
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/11239/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7738623&buildTypeId=IgniteTests24Java8_RunAll]
> Replacing currentTimeMillis() with nanoTime() in LongJVMPauseDetector
> ---------------------------------------------------------------------
>
> Key: IGNITE-21475
> URL: https://issues.apache.org/jira/browse/IGNITE-21475
> Project: Ignite
> Issue Type: Improvement
> Reporter: Oleg Valuyskiy
> Assignee: Oleg Valuyskiy
> Priority: Minor
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To improve the mechanism of JVM pause detection, it’s recommended to replace
> System.System.currentTimeMillis() with System.nanoTime() in the
> ‘LongJVMPauseDetector’ class, since currentTimeMillis() is not monotonic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
