You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/01/10 11:51:00 UTC
[jira] [Commented] (IGNITE-10537) MVCC: Client reconnect tests
became unstable after mvcc coordinator reassign fix.
[ https://issues.apache.org/jira/browse/IGNITE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739322#comment-16739322 ]
Ignite TC Bot commented on IGNITE-10537:
----------------------------------------
{panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests 7|https://ci.ignite.apache.org/viewLog.html?buildId=2759956]]
* IgniteCacheMvccSqlTestSuite: CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups0_RestartCoordinator_ScanDml - 0,0% fails in last 568 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_SqlDml - 0,0% fails in last 568 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups0_RestartCoordinator_ScanDml - 0,0% fails in last 568 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_ScanDml_Persistence - 0,0% fails in last 568 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups2_RestartCoordinator_SqlDml_Persistence - 0,0% fails in last 568 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_SingleNode_RestartCoordinator_SqlDml_Persistence - 0,0% fails in last 568 master runs.
{color:#d04437}MVCC Cache{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2759962]]
* IgniteCacheMvccTestSuite: CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_Scan - 0,0% fails in last 573 master runs.
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2759960]]
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2669542&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Client reconnect tests became unstable after mvcc coordinator reassign fix.
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-10537
> URL: https://issues.apache.org/jira/browse/IGNITE-10537
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Igor Seliverstov
> Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> It looks like tests [CacheMvccContinuousQueryClientReconnectTest.testReconnectClient|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7778544852295951300&tab=testDetails] and [CacheMvccContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-8370258276605466922&tab=testDetails] became flaky after commit _5477048 rkondakov <ko...@mail.ru> on 22.11.18 at 14:35_. Weshould investigate and fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)