You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2017/07/21 11:03:00 UTC
[jira] [Updated] (IGNITE-5800) Umbrella ticket for making Teamcity
Green Again
[ https://issues.apache.org/jira/browse/IGNITE-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov updated IGNITE-5800:
-----------------------------------
Description:
*Discussions*
http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html
http://apache-ignite-developers.2346864.n4.nabble.com/Make-Teamcity-Green-Again-td19873.html
*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
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=%3Cdefault%3E
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 blocked to the next release, test should be muted.
- 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*
TBD by JIRA queries
was:
*Discussions*
http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html
http://apache-ignite-developers.2346864.n4.nabble.com/Make-Teamcity-Green-Again-td19873.html
*Goal*
To allow community grow more quickly and from the CI perspective, failing tests should be the main concern
For Run All dependencies at Ignite 20 Tests
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=%3Cdefault%3E
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 blocked to the next release, test should be muted.
- 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*
TBD by JIRA queries
> Umbrella ticket for making Teamcity Green Again
> -----------------------------------------------
>
> Key: IGNITE-5800
> URL: https://issues.apache.org/jira/browse/IGNITE-5800
> Project: Ignite
> Issue Type: Wish
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
>
> *Discussions*
> http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html
> http://apache-ignite-developers.2346864.n4.nabble.com/Make-Teamcity-Green-Again-td19873.html
> *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
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=%3Cdefault%3E
> 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 blocked to the next release, test should be muted.
> - 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*
> TBD by JIRA queries
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)