ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kondakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11079) MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
Date Tue, 12 Mar 2019 18:44:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790866#comment-16790866
] 

Roman Kondakov commented on IGNITE-11079:
-----------------------------------------

Problem: The problem was that [implemented optimization|https://github.com/gridgain/apache-ignite/commit/42293fac88c29544b7c55c0340224afbf474a301]
of storing filtered events in the backup queues was not taken into account for this test.
After this optimization backups do not store all filtered events and instead storing they
use {{filtered}} counter. In this case the expectation of the large size of backup queues
is wrong.

Fix: fixed the expectation of backup queues total size - it should be small or even zero.

 Since the only test code was changed, the RunAll visa from the TC Bot is not necessary.
I've runned two relevant suites (mvcc and non-mvcc). Waiting for results:

[https://ci.ignite.apache.org/viewLog.html?buildId=3298494&tab=queuedBuildOverviewTab]

[https://ci.ignite.apache.org/viewLog.html?buildId=3298496&buildTypeId=IgniteTests24Java8_ContinuousQuery3]

> MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
> ----------------------------------------------------------
>
>                 Key: IGNITE-11079
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11079
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Andrew Mashenkov
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> See Tc run
>  [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=925274886589214180&tab=testDetails]
> Test fails after series of long JVM pauses with stacktrace:
> {code:java}
> junit.framework.AssertionFailedError
>  at junit.framework.Assert.fail(Assert.java:55)
>  at junit.framework.Assert.assertTrue(Assert.java:22)
>  at junit.framework.Assert.assertTrue(Assert.java:31)
>  at org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryBackupQueueTest.testManyQueryBackupQueue(IgniteCacheContinuousQueryBackupQueueTest.java:175)
>  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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>  at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>  at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>  at org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
>  at java.lang.Thread.run(Thread.java:748){code}



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

Mime
View raw message