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

Ignite TC Bot commented on IGNITE-10693:
----------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3077502]]
* IgnitePdsTestSuite2: 
IgniteWalHistoryReservationsTest.testNodeLeftDuringExchange - 0,0% fails in 
last 415 master runs.

{color:#d04437}Queries 2{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=3077445]]
* IgniteBinaryCacheQueryTestSuite2: 
IgniteCacheQueryNodeRestartSelfTest.testRestarts - 0,0% fails in last 416 
master runs.
* IgniteBinaryCacheQueryTestSuite2: 
IgniteChangingBaselineCacheQueryNodeRestartSelfTest.testRestarts - 0,0% fails 
in last 416 master runs.
* IgniteBinaryCacheQueryTestSuite2: 
DynamicIndexPartitionedTransactionalConcurrentSelfTest.testCoordinatorChange - 
0,0% fails in last 416 master runs.
* IgniteBinaryCacheQueryTestSuite2: 
DynamicIndexPartitionedAtomicConcurrentSelfTest.testCoordinatorChange - 0,0% 
fails in last 416 master runs.

{color:#d04437}Cache 5{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3077487]]
* IgniteCacheWithIndexingTestSuite: 
CacheTtlAtomicPartitionedSelfTest.testDefaultTimeToLivePreload - 0,0% fails in 
last 417 master runs.
* IgniteCacheWithIndexingTestSuite: 
IgniteClientReconnectQueriesTest.testReconnectQueryInProgress - 0,0% fails in 
last 417 master runs.
* IgniteCacheWithIndexingTestSuite: 
IgniteClientReconnectQueriesTest.testQueryReconnect - 0,0% fails in last 417 
master runs.

{color:#d04437}JDBC Driver{color} [[tests 
6|https://ci.ignite.apache.org/viewLog.html?buildId=3077442]]
* IgniteJdbcDriverTestSuite: JdbcComplexQuerySelfTest.testBetween - 0,0% fails 
in last 418 master runs.
* IgniteJdbcDriverTestSuite: JdbcComplexQuerySelfTest.testJoinWithoutAlias - 
0,0% fails in last 418 master runs.
* IgniteJdbcDriverTestSuite: JdbcComplexQuerySelfTest.testJoin - 0,0% fails in 
last 418 master runs.
* IgniteJdbcDriverTestSuite: JdbcComplexQuerySelfTest.testIn - 0,0% fails in 
last 418 master runs.
* IgniteJdbcDriverTestSuite: JdbcDistributedJoinsQueryTest.testJoin - 0,0% 
fails in last 418 master runs.
* IgniteJdbcDriverTestSuite: JdbcComplexQuerySelfTest.testCalculatedValue - 
0,0% fails in last 418 master runs.

{color:#d04437}Spring{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3077446]]

{color:#d04437}MVCC PDS 4{color} [[tests 0 TIMEOUT , Exit Code , 
BUILD_RUNNER_ERROR |https://ci.ignite.apache.org/viewLog.html?buildId=3077533]]

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3077535&buildTypeId=IgniteTests24Java8_RunAll]

> MVCC TX: Random server restart tests became failed
> --------------------------------------------------
>
>                 Key: IGNITE-10693
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10693
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc, sql
>            Reporter: Igor Seliverstov
>            Assignee: Igor Seliverstov
>            Priority: Major
>              Labels: failover, mvcc_stabilization_stage_1
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7945125576049372508&branch=%3Cdefault%3E&tab=testDetails],
>  
> [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=8412476034648229784&branch=%3Cdefault%3E&tab=testDetails],
>  
> [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=254244004184327163&branch=%3Cdefault%3E&tab=testDetails],
>  all these tests became failed after IGNITE-9630 has been merged to master.
> Seems there is an issue in partition calculating mechanism on unstable 
> topology. I suppose the algorithm uses partitions on nodes just become 
> primary while the partitions are in moving state.



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

Reply via email to