You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Created vs Resolved Issues Chart

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

 

Table of Contents

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 - 50-100% of failures - issue is to be created as blocker to the next release, test may be muted after research.
  • Flaky tests 1%-50% of failures, which are considered by teamcity as flaky may be not muted for now because TC interface helps us to identify these tests.

Scope

Unassigned issues

key summary type created updated due assignee reporter priority status resolution

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

Currently failing tests

type key summary assignee reporter priority status resolution created updated due

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

Muted failures

key summary type created updated due assignee reporter priority status resolution

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

  • No labels

Apache Ignite