ignite-pr-checker commented on PR #13785: URL: https://github.com/apache/ignite/pull/13785#issuecomment-6776705014
@anton-vinogradov **[Ignite PR Checker](https://ignite-pr-checker.is-a.dev/?pr=13785)** verdict · RunAll build [9486523](https://ci2.ignite.apache.org/build/9486523) · tested [405b249](https://github.com/apache/ignite/pull/13785/commits/405b249a2b0351b11f41f356f65650d364cb2d8d) · 149 suites ran, 0 reused ⚠️ **This run doesn't cover the PR fully:** - mixed run — Cache 21, Control Utility 1 and PDS (Compatibility) re-ran on 86035ce, the rest of the RunAll ran on 405b249; only a RunAll of the PR's head can prove it clean Everything below is what it did manage to say. ❌ **4 blockers in 1 suite:** - Control Utility 1 · `CommandHandlerParsingTest` — 4 tests: `testParseAndValidateSSLArguments`, `testConnectionSettings`, `testParseAndValidateUserAndPassword` and 1 more · [TC](https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/9486543?buildTab=tests) <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 `86035ce`._ _♻️ Settled after 2 auto re-run waves: #1 — 3 suites that failed mid-run; #2 — 1 suite with tests that started failing._ ➡️ **Next:** fix the blockers, push, and run RunAll again — a `/run-all` comment here does it when PR commands are on in the checker's ⚙. -- 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]
