[
https://issues.apache.org/jira/browse/IGNITE-28762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089207#comment-18089207
]
Ignite TC Bot commented on IGNITE-28762:
----------------------------------------
{panel:title=Branch: [pull/13228/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13228/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=9118858&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9118858
rerunBuildIds=none{color}
> Flaky PageMemoryNoStoreLeakTest.testPageDoubleInitMemoryLeak
> ------------------------------------------------------------
>
> Key: IGNITE-28762
> URL: https://issues.apache.org/jira/browse/IGNITE-28762
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test PageMemoryNoStoreLeakTest.testPageDoubleInitMemoryLeak is flaky. In this
> test process commited memory metric is used to detect memory leak, but a lot
> of other subsystems affect this metric, including heap memory allocation. So,
> we can't rely on this metric to detect memory leakage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
