[
https://issues.apache.org/jira/browse/IGNITE-9659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658783#comment-16658783
]
Ignite TC Bot commented on IGNITE-9659:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}~[Excluded] Inspections: AOP{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2133722]]
{color:#d04437}~[Excluded] Inspections: Core{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2133725]]
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2119447&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
