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

Pavel Tupitsyn updated IGNITE-17402:
------------------------------------
    Description: 
Failed then succeeded without changes:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunUnitTests/6691262

{code}
org.opentest4j.AssertionFailedError: expected: <s2> but was: <s1>
  at 
org.apache.ignite.client.ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists(ClientComputeTest.java:71)
{code}

  was:
Failed then succeeded without changes:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunUnitTests/6691262

org.opentest4j.AssertionFailedError: expected: <s2> but was: <s1>
  at 
org.apache.ignite.client.ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists(ClientComputeTest.java:71)


> Thin 3.0: testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists is 
> flaky
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-17402
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17402
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 3.0.0-alpha6
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>
> Failed then succeeded without changes:
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunUnitTests/6691262
> {code}
> org.opentest4j.AssertionFailedError: expected: <s2> but was: <s1>
>   at 
> org.apache.ignite.client.ClientComputeTest.testClientSendsComputeJobToTargetNodeWhenDirectConnectionExists(ClientComputeTest.java:71)
> {code}



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

Reply via email to