Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Discussions

Accordig to discussions Test failures and MakeTeamcityGreenAgain

Goal
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

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = IGNITE AND labels = MakeTeamcityGreenAgain and labels != Muted_Test AND assignee is EMPTY AND resolution is EMPTY
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

 

Currently failing tests

Jira
serverASF JIRA
jqlQueryproject = IGNITE and labels = MakeTeamcityGreenAgain and labels != Muted_test and resolution is EMPTY
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

 

Muted failures

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = IGNITE and labels = MakeTeamcityGreenAgain and labels != Muted_test and resolution is EMPTY
serverId5aa69414-a9e9-3523-82ec-879b028fb15b