[
https://issues.apache.org/jira/browse/IGNITE-26959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18064342#comment-18064342
]
Ignite TC Bot commented on IGNITE-26959:
----------------------------------------
{panel:title=Branch: [pull/12861/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12861/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=8914658&buildTypeId=IgniteTests24Java8_RunAll]
> Test TestLongEventsProcessingDisconnect from C++ test suite is broken in
> master
> -------------------------------------------------------------------------------
>
> Key: IGNITE-26959
> URL: https://issues.apache.org/jira/browse/IGNITE-26959
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Kirill Anisimov
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> According to
> [history|https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5112321148966502234&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
> this test is broken in master branch since 22 October 2025.
> One possible culprit is a [refactoring
> commit|https://github.com/apache/ignite/commit/0b5b218254dd49695e83ea1baa1319ffabc6ffa0#diff-37f047534e3320d3378962125b64f64028d3e51a25c694d66e83ea84f49b55df]
> that broke behavior of catching exceptions when cleaning up resources, but
> more investigation is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
