You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Amelchev Nikita (JIRA)" <ji...@apache.org> on 2018/10/16 14:38:00 UTC

[jira] [Updated] (IGNITE-9659) NonCollocatedRetryMessageSelfTest is flaky

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

Amelchev Nikita updated IGNITE-9659:
------------------------------------
    Fix Version/s: 2.8

> NonCollocatedRetryMessageSelfTest is flaky
> ------------------------------------------
>
>                 Key: IGNITE-9659
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9659
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Alexey Goncharuk
>            Assignee: Amelchev Nikita
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1881869&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Queries2#testNameId-2853122976880171731
> A few concerns on the test code:
> 1) What is the point of setting an anonymous discovery SPI? The overridden method is identical to super(), but the new discovery SPI looses test VM IP finder which is set by default
> 2) Looks like there is a race in test communication SPI code - there is an if - assign block for a volatile variable
> 3) The test fails with "Node left during query execution" - since the node is stopped, this should be either an allowed exception, or the test communication SPI should be crafted more carefully.
> (FYI: Locally I have this test failing with No CacheException emitted. Collection size=10)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)