[
https://issues.apache.org/jira/browse/IGNITE-16483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489951#comment-17489951
]
Ignite TC Bot commented on IGNITE-16483:
----------------------------------------
{panel:title=Branch: [pull/9810/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9810/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Compute (Grid){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6409982]]
* {color:#013220}IgniteBinaryObjectsComputeGridTestSuite:
ComputeGridMonitorTest.simpleClientNodeTest - PASSED{color}
* {color:#013220}IgniteBinaryObjectsComputeGridTestSuite:
ComputeGridMonitorTest.snapshotsClientNodeTest - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6410044&buildTypeId=IgniteTests24Java8_RunAll]
> Improve ComputeGridMonitor test coverage
> ----------------------------------------
>
> Key: IGNITE-16483
> URL: https://issues.apache.org/jira/browse/IGNITE-16483
> Project: Ignite
> Issue Type: Bug
> Components: compute
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Minor
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Fix flaky *ComputeJobChangePriorityTest#testChangeTaskPriorityAttribute*
> The problem is in the test itself, there could be a rare race between
> completing a compute task and waiting for its attribute, so it was enough to
> add task completion after receiving the expected attribute.
> Add tests for *ComputeGridMonitor* in case of a client node.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
