[ 
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PetrovMikhail updated IGNITE-10243:
-----------------------------------
    Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209639]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite: 
IgniteClientReconnectCacheQueriesFailoverTest.testReconnectCacheQueries
* IgniteBinarySimpleNameMapperCacheQueryTestSuite: 
IgniteErrorOnRebalanceTest.testErrorOnRebalance

{color:#d04437}MVCC Queries{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209591]]
* IgniteCacheMvccSqlTestSuite: 
CacheMvccContinuousWithTransformerReplicatedSelfTest.testContinuousWithTransformerAndRegularListenerKeepBinaryAsync

{color:#d04437}Continuous Query 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3: 
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync - 
0,0% fails in last 100 master runs.

{color:#d04437}SPI{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2331419]]
* IgniteSpiTestSuite: 
IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1

{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209538]]
* IgniteBinarySimpleNameMapperBasicTestSuite: 
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChangeFail

{color:#d04437}Start Nodes{color} [[tests 
16|https://ci.ignite.apache.org/viewLog.html?buildId=2209571]]
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in 
last 100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in 
last 100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall - 
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last 
100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last 
100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in 
last 100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last 
100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails 
in last 100 master runs.
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails 
in last 100 master runs.

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

> [TC Bot] Support partially cancelled suites in RunAll
> -----------------------------------------------------
>
>                 Key: IGNITE-10243
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10243
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we 
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds 
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use 
> this one as a possible blocker for PR report.



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

Reply via email to