...

For Run All dependencies at Ignite 20 Tests there should be no stable red suites. timed out suites and stable red tests.

Issue Priorities
Following priorities are suggested for issues:

• Test suite timeout - it hides real test failures from us and wastes agent time
• Stable failing test/flaky - 10%-100% of failures - issue is to be created as blocker to the next release, test may be muted after research.
• Rare Flaky tests 1%-10% of failures, which are considered by teamcity as flaky may be not muted for now because TC interface helps us to identify these tests.

MTCGA Bot

For early identification of failures, for master and release branch monitoring there is special tool MTCGA Bot (Ignite TC Helper).

...

This tool can be also used for checking PR for introduction of new failures.

Notification Types

This section covers notification types utility can send to dev@ list. User can specify his or her email and select desired tracked branches. All failures in this braches will be also forwarded to user.

New test failure notification

New test failure notification is generated if test was stable passing and then became stable failing. Stable passing test requires at least 5 sucessfull runs in a row. Stable failure requires 3 failures in a row.

Let's define 0 as success, 1 as failure. 

So history of runs ..00000111.. will cause notification. First transition 0->1 can be bug introduced test failure, and notification is linked to this particular build. Notification will not be resend in case tests continues to fail. This is done because all contributors are considered as interested in successfull tests passing and will do required steps to fix issue.

Duplicate notification can occur for same test if there is history ...00000111...00000111.  And second transition 0 ->1 can be potentially new problem, and test failure would be re-notified.

Flaky test failure notification

Some tests are flaky and sometimes change its state. This means test can be unluckily failed 3 times in a row. To protect from spam the Bot checks if test status transition is not often. Heuristic rule now is more than 6 state transitions for latest 50 runs. If test will change its state often then new rule is applied. Test fail is considered as fail for 7 failures in a row. So history should be at least ...000001111111... 

Newly contributed tests faillure

If test has no previous history and failed 3 times in a row, then it should be also considered as newly introduced failure. This notification is planned to be supported in future releases: https://github.com/dspavlov/ignite-teamcity-helper/issues/10

Critical suite failure

The Bot is able to handle timeouts & JVM crashes in suites in a special way. These type of failures are named Critical.  If 3 or more (timeouts/JMV crashes) occured several times in a row, this will generate suite-related notification. Also it is required that last run was completed with timeout.

Lets name result 2 as critical failure. So it is required to have 5 non critical failures and 3 critical to generate notification: ....(0/1)(0/1)(0/1)(0/1)(0/1) 222....

Scope

Unassigned issues

project = IGNITE AND labels = MakeTeamcityGreenAgain AND assignee is EMPTY AND resolution is EMPTY 

...