[
https://issues.apache.org/jira/browse/IGNITE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660509#comment-16660509
]
ASF GitHub Bot commented on IGNITE-9976:
----------------------------------------
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/5056
IGNITE-9976
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9976
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5056.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5056
----
commit c24984e0bdb53cc3c4d9814a8efaa93132de056d
Author: pereslegin-pa <xxtern@...>
Date: 2018-10-23T11:54:27Z
IGNITE-9976 Flaky failure fix.
----
> [Test Failed] BinaryMetadataUpdatesFlowTest.testFlowNoConflicts flaky fails
> on TC.
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-9976
> URL: https://issues.apache.org/jira/browse/IGNITE-9976
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Test {{BinaryMetadataUpdatesFlowTest.testFlowNoConflicts}} fails sometimes on
> master branch.
> Example of recent failure:
> https://ci.ignite.apache.org/viewLog.html?buildId=2136137&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_BinaryObjects#testNameId-3561618975502992496
> Typical output:
> {noformat}
> [2018-10-20 16:26:55,321][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: There are less than expected entries,
> data loss occurred; expected:<5000> but was:<4108>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataUpdatesFlowTest.testFlowNoConflicts(BinaryMetadataUpdatesFlowTest.java:309)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:142)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2091)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> With {{PRIMARY_SYNC}} cache write synchronization mode on unstable topology
> we should await {{PME}} before call {{size()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
