You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/23 06:48:00 UTC
[jira] [Commented] (IGNITE-8025) Result of
GridTestUtils.runMultiThreadedAsync has a bug in cancel() implementation
[ https://issues.apache.org/jira/browse/IGNITE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410892#comment-16410892 ]
ASF GitHub Bot commented on IGNITE-8025:
----------------------------------------
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3687
IGNITE-8025 runMultiThreadedAsync cancellation fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8025
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3687.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3687
----
commit 2b6dd75e80a1b59ec04c2a5a8d9cf147b736822d
Author: Andrey Kuznetsov <st...@...>
Date: 2018-03-23T06:46:41Z
IGNITE-8025 runMultiThreadedAsync cancellation fix.
----
> 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)