[
https://issues.apache.org/jira/browse/IGNITE-28189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066059#comment-18066059
]
Ignite TC Bot commented on IGNITE-28189:
----------------------------------------
{panel:title=Branch: [pull/12876/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12876/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=8926604&buildTypeId=IgniteTests24Java8_RunAll]
> Incorrect status of a Compute Task when it is canceled
> ------------------------------------------------------
>
> Key: IGNITE-28189
> URL: https://issues.apache.org/jira/browse/IGNITE-28189
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> We need to fix flaky SecurityCommandHandlerPermissionsTest#testTaskCancel -
> see
> https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-773396541916445812&tab=testDetails
> for more details.
> The test failures are caused by a race condition between job cancellation and
> completion. The failure can be easily reproduced by adding a "sleep" in the
> org.apache.ignite.internal.processors.job.GridJobWorker#cancel(boolean)
> method before super.cancel() call.
> The race condition described above can result in a task successfully
> completing with no cancelled mark even though it was explicitly canceled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
