[
https://issues.apache.org/jira/browse/IGNITE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418681#comment-16418681
]
Dmitriy Pavlov commented on IGNITE-8025:
----------------------------------------
I've found 2 suspicious tests
Binary Objects (Simple Mapper Queries) [ tests 4 ]
...
IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteCacheLocalQueryCancelOrTimeoutSelfTest.testQueryCancelZeroTimeout (master
fail rate 0,0%)
IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteSqlSplitterSelfTest.testReplicatedTablesUsingPartitionedCacheClient
(master fail rate 0,0%)
Could you please check if these failures not related to change?
> Result of GridTestUtils.runMultiThreadedAsync has a bug in cancel()
> implementation
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-8025
> URL: https://issues.apache.org/jira/browse/IGNITE-8025
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Andrey Kuznetsov
> Assignee: Andrey Kuznetsov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, test
> Fix For: 2.5
>
> Attachments: BugRunMTAsyncTest.java
>
>
> GridTestUtils.runMultiThreadedAsync returns a future with cancel() support,
> but cancellation implementation never interrupts threads that execute
> user-provided tasks. That is, those threads can continue their execution even
> after test method finishes.
> The reproducer attached demonstrates activity from threads created by test0
> after test0 finished and test1 is being run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
