ignite-pr-checker commented on PR #13786: URL: https://github.com/apache/ignite/pull/13786#issuecomment-6933574423
@anton-vinogradov **[Ignite PR Checker](https://ignite-pr-checker.is-a.dev/ignite?pr=13786)** verdict · RunAll build [9503179](https://ci2.ignite.apache.org/build/9503179) · tested [66d0088](https://github.com/apache/ignite/pull/13786/commits/66d0088ba3d8066bac33c07d1fa344b24ebf0a74) · 149 suites ran, 0 reused ⚠️ **This run doesn't cover the PR fully:** - 2 suites have no reliable result (2× execution timeout · non-zero exit code) - mixed run — Client Nodes, PDS 9, Thin client: Node.js and 1 more suite re-ran on 1db740d, the rest of the RunAll ran on 66d0088; only a RunAll of the PR's head can prove it clean Everything below is what it did manage to say. ⚠️ **Broken suites** (no reliable result): - execution timeout · non-zero exit code (2 suites): Thin client: Node.js, \[Check Code Style Ducktests\] 🔎 **No blockers found — but the run above can't prove the PR is clean.** 113 failing tests are not blamed on this PR. Re-run after you handle what is listed above. <sub>What each label means and what to do: [verdict glossary](https://github.com/anton-vinogradov/ignite-pr-checker/blob/main/docs/features.md#verdict-glossary).</sub> _The PR is now at `1db740d`._ _♻️ Settled after 2 auto re-run waves: #1 — 8 suites that failed mid-run; #2 — 2 broken suites._ -- 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]
