[
https://issues.apache.org/jira/browse/IGNITE-28883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18096086#comment-18096086
]
Ignite TC Bot commented on IGNITE-28883:
----------------------------------------
{panel:title=Branch: [pull/13360/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13360/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=9203800&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9203800
rerunBuildIds=none{color}
> Stabilize Ignite Features related tests
> ---------------------------------------
>
> Key: IGNITE-28883
> URL: https://issues.apache.org/jira/browse/IGNITE-28883
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: IEP-132, ise
> Fix For: 2.19
>
> Attachments: reproducer.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The attached reproducer increases chances of Ignite Features tests
> instability by relying only on sleeps. And can be considered as a reproducer.
> org.apache.ignite.internal.processors.rollingupgrade.CoreVersionRollingUpgradeTest#testConcurrentFinalizationErrorPreserveNodeFence
> and
> org.apache.ignite.internal.processors.rollingupgrade.CoreVersionRollingUpgradeTest#testClientNodeClearsActiveFinalizationProcessOnDisconnect
> tests are the most susceptible to this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
