oleg-vlsk commented on PR #13583:
URL: https://github.com/apache/ignite/pull/13583#issuecomment-5988407597

   **[Ignite PR Checker](https://ignite-pr-checker.is-a.dev/?pr=13583)** 
verdict · RunAll build [9386823](https://ci2.ignite.apache.org/build/9386823) · 
147 suites ran, 0 reused
   
   ⚠️ **This run doesn't cover the PR fully:**
   - 1 suite(s) have no reliable result (compilation error, timeout, crash)
   - a newer run is still going — its unfinished suites can still fail
   - 2 commit(s) pushed since this run — it tested older code
   
   Everything below is what it did manage to say.
   
   ⚠️ **1 broken suite(s)** (no reliable run):
   - Cache (Failover) 4: execution timeout · non-zero exit code · Number of 
tests 17 is 55% less than 38 in build #1232 — ran 17 of master's 38 tests
   
   👀 **4 test(s) started failing on this code** — not proven blockers yet: too 
few runs of this revision to tell a break from a flake, so a re-run of the 
suite decides it.
   - Platform .NET (Windows): `Apache.Ignite.Core.Tests.exe: 
Apache.Ignite.Core.Tests.Cache.Platform.PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(1)`
   - PDS 10: `org.apache.ignite.testsuites.IgnitePdsTestSuite10: 
org.apache.ignite.cdc.WalForCdcTest.testOnlyDataRecordWritten[mode=REPLICATED, 
atomicityMode=TRANSACTIONAL]`
   - Data Structures 2: 
`org.apache.ignite.testsuites.IgniteCacheDataStructuresSelfTestSuite2: 
org.apache.ignite.internal.processors.cache.datastructures.partitioned.GridCachePartitionedQueueEntryMoveSelfTest.testQueue`
   - Cache (Tx Recovery): 
`org.apache.ignite.testsuites.IgniteCacheTxRecoverySelfTestSuite: 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheTxRecoveryRollbackTest.testNearTx1Optimistic`
   
   ⚠️ **No proven blocker yet** — this is not an all-clear: see the tests 
above. 18 pre-existing/flaky filtered out.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to