See which tests your Apache Ignite PR actually broke, not the ones already failing or flaky on master. Start a RunAll or rerun just the blockers, right from here.
Log in with your own TeamCity (ci2) access token. There is no shared account: TeamCity records the runs you start or cancel here as yours. The server also uses your token to read TeamCity for everyone's PRs, for up to an hour after your last request.
What the checker does with your token
- Your browser keeps it in an encrypted session cookie.
- The server keeps it in memory for up to an hour after your last request, or until you log out. The host's swap can write that memory to the disk.
- After login, the ⚙ menu has options that work while this page is closed. While one is on, the server stores the token encrypted, until you turn them all off. Copies stay in server backups until the backups are replaced. With any option other than PR commands on, the server also keeps using the token to read from TeamCity, to check open PRs for everyone.
- Your login ends when you log out (in every browser at once) or after 400 days without use.
No ci2 account or token yet?
- Register an account on ci2, the TeamCity of Apache Ignite.
- Create an access token there: Profile → Access Tokens (“Create a token” above opens it).
- The token acts with your account's rights. Reading verdicts needs only view access; Run and Rerun need the right to run builds, “Run at top” and “Rerun at top” also to reorder the build queue (without it, TeamCity queues them at the end), and “Cancel my runs” to stop builds and remove them from the queue.
An open-source developer tool for Apache Ignite contributors (source on GitHub). It reads test results from Ignite's CI server, TeamCity (ci2).
? JIRA visa: JIRA visa: the PR title names no IGNITE ticket.
⚠ Suites that never ran ?
Broken suites ?
Rerun these first: the verdict above can't see their tests. A compilation error needs a code fix instead, so it has no Rerun.
Fewer tests than master ?
Tests that did not run cannot fail. Nothing to do if this PR removes tests on purpose. If not, compare the test list with master and rerun.
Blockers ? Group by:
Not confirmed yet: each of these failed its only run on this branch. Rerun their suites: a second failure confirms a blocker, a pass removes it.
Not confirmed: 1 run ?
Each failed its only run on this branch. Rerun their suites: a second failure confirms a blocker, a pass removes it.
Recently started failing ?
Not blockers yet: there are too few runs of this code to tell a break from a flake. Rerun their suites: if they keep failing, they become blockers; if they pass, they drop out.
Could not be checked ?
These tests failed, but TeamCity errors stopped the check. They are not counted as blockers. The checker tries again by itself.
This PR's tests ?
Crashed near the end of the run — results stand ?
None of their failures is blamed on this PR (see Not blamed on this PR), so the results of the tests they ran stand. Nothing to do.