[jira] [Updated] (IGNITE-16939) ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists is flaky

["Stanislav Lukyanov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stanislav Lukyanov updated IGNITE-16939:
----------------------------------------
    Fix Version/s:     (was: 3.0.0-beta1)

> ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists is flaky
> ------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-16939
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16939
>             Project: Ignite
>          Issue Type: Bug
>          Components: clients
>            Reporter: Roman Puchkovskiy
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>
> See [https://ci.ignite.apache.org/viewLog.html?buildId=6560290&buildTypeId=ignite3_Test_RunUnitTests]
> {code:java}
> org.opentest4j.AssertionFailedError
> org.opentest4j.AssertionFailedError: expected: <s2> but was: <s1>
>   at org.apache.ignite.client.ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists(ClientComputeTest.java:68)
> {code}
> The branch is main with one commit which disables one test, so it's equivalent to main branch in everything that concerns the failed test.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)