/run-all (or /runall) — queue the whole RunAll chain, under my own
TeamCity token;
/run-all top — the same, entering the build queue at the top;
/top — move the run my command started to the top of the queue (while it is
still queued). Nobody else's builds are ever touched.
Commands need my GitHub login. With the option above ON it's taken from the token; without a
token, link it here:
Ack: 🚀 reaction = accepted, 😕 = refused or nothing to act on. The TC link and a live
"~1h 23m remaining — ≈ 21:05 MSK" line (in my JIRA-profile timezone) are edited into the command
comment itself; the verdict is one living comment that updates through the auto re-runs — two
messages per run, total. Commands are picked up within a minute, on any pull request.
See which tests your Apache Ignite PR actually broke —
not the ones already failing or flaky on master.
Trigger a RunAll or re-run just the blockers, right from here.
An open-source continuous-integration tool for
Apache Ignite
contributors — source on
GitHub.
It reads the project's TeamCity CI (ci2) to tell real regressions from pre-existing flaky failures.
Log in with your own TeamCity (ci2) access token.
Everything runs under your account — there is no shared server token.
It is kept encrypted in your session cookie, never on the server.
Your login lasts until you log out.
Pick a PR on the left — or search below.
RunAll:
⚠ RunAll interrupted
Broken suites
Didn't complete a reliable run — compilation, timeout, out-of-memory, crash or infrastructure.
A timed-out or crashed suite is shown here rather than mined for blockers (its failures would be hang cascade,
and some tests never ran). Re-run these first: the verdict below can't trust what they would have found.
Fewer tests than master
These suites ran noticeably fewer tests than the same suites run on master. Tests that never
ran can't fail — a suite can look green while silently skipping coverage (a broken suite class, an excluded
package, a run that ended early). Intentional if this PR removes tests; otherwise re-run and check.
Blockers
Posting a visa needs your JIRA Personal Access Token —
create one in your ASF JIRA profile,
then paste it here (kept encrypted in your session cookie, never stored server-side):
Nothing in this run looks caused by your PR — good to go.
Recently started failing
Failing the last few runs on this branch but passing earlier — a fresh break to watch,
not yet a steady blocker. If it keeps failing it becomes a blocker; if it flaps back it won't.