[
https://issues.apache.org/jira/browse/IGNITE-29271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142803#comment-18142803
]
Ignite TC Bot commented on IGNITE-29271:
----------------------------------------
{panel:title=Branch: [pull/13811/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13811/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=9486693&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9486693
rerunBuildIds=9487749,9487751,9487753{color}
> Fix flaky ClusterMetricsSelfTest
> --------------------------------
>
> Key: IGNITE-29271
> URL: https://issues.apache.org/jira/browse/IGNITE-29271
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Fix For: 2.20
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridDhtPartitionsExchangeFuture#onDone}} updates the {{DurationHistogram}}
> and {{CacheOperationsBlockedDurationHistogram}} metrics only after
> {{super.onDone()}}, so the test, which waits for the {{Duration}} metric to
> drop to zero (that is, for {{isDone()}}) and then reads the histograms,
> sporadically sees the previous counts. The {{CacheOperationsBlockedDuration}}
> check has the same race: {{GridCachePartitionExchangeManager}} publishes a
> new exchange future as {{lastTopologyFuture()}} before {{init()}} sets
> {{initTime}}, and until then {{currentPMEDuration(true)}} returns zero.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
