[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689335#comment-16689335
]
Ignite TC Bot commented on IGNITE-10243:
----------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2316244]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelay
- 0,0% fails in last 100 master runs.
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316252]]
* IgniteCacheMvccTestSuite:
CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence
- 1,4% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=2316267]]
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testNodeAttributes - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testLocalMetricsUpdate - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionTimeoutEnabled - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketWrite - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testConnectionCheckMessage - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketOpen - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiFailureTimeoutSelfTest.testNodeAttributes
- 1,0% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testDiscovery - 1,0% fails in
last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiConfigSelfTest.testLocalPortRange - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache (Full API){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316355]]
* IgniteCacheFullApiSelfTestSuite:
GridCacheLocalWithGroupFullApiSelfTest.testTtlTx - 0,0% fails in last 100
master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2316273]]
*
JdbcThinTransactionsServerAutoCommitComplexSelfTest.testRepeatableReadWithConcurrentCacheReplace
(last started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157&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)
