Created vs Resolved Issues Chart

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Table of Contents

Introduction

Goal

Accordig to discussions Test failures and MakeTeamcityGreenAgain To allow community to grow more quickly and from the CI perspective, failing tests should be the main concern

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

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 monitors TeamCity https://ci.ignite.apache.org/ and send notifications to dev. list if it detects new failures.

Source code available at https://github.com/dspavlov/ignite-teamcity-helper

Ignite Developers are welcome to give feedback and post issues: https://github.com/dspavlov/ignite-teamcity-helper/issues

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

Scope

Unassigned issues

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

Assigned failing tests

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

Muted failures

project = IGNITE and labels = MakeTeamcityGreenAgain and labels = Muted_test and resolution is EMPTY