[
https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655585#comment-16655585
]
Alexey Goncharuk commented on IGNITE-9769:
------------------------------------------
[~SomeFire], I think we are a tiny step away from the correct solution :) Let's
create a method in {{GridCommonAbstractTest}} that will wait for the proper
affinity version and use it in this test (something similar is done in
{{CacheLateAffinityAssignmentTest#testAffinitySimpleNoCacheOnCoordinator1}}).
Otherwise, the test will become flaky again if we speed up client start, for
example.
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
> -----------------------------------------------------------
>
> Key: IGNITE-9769
> URL: https://issues.apache.org/jira/browse/IGNITE-9769
> Project: Ignite
> Issue Type: Task
> Reporter: Ryabov Dmitrii
> Assignee: Ryabov Dmitrii
> Priority: Trivial
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate1}} and
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate2}} are flaky.
> In the {{#readerUpdateDhtFails}} method we blocks
> {{GridDhtAtomicNearResponse}} messages and do put operation. Put should hangs
> always, but sometimes it doesn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
