Odd flaky tests notifications were fixed.

If test changes its status more than 6 times in last 50 runs, than it is
required to fail 7 times in a row to be considered as new failure. Normal
test can be considered as new failure if it fails 3 times.

I would appreciate any feedback and proposals of rules change to make
MTCGA.Bot as useful as it humanly possible.

вт, 17 июл. 2018 г. в 10:26, Dmitry Pavlov <[email protected]>:

> Hi Igniters,
>
> Seems this test is flaky: it has frequent changes of its status. This can
> be detected in Bot. and I'll update Bot once issue
> https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is completed.
>
> So please ignore this failure for now, as it is not new. Of course if you
> know how to fix flakiness, fix is always preferred.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> вт, 17 июл. 2018 г. в 2:06, <[email protected]>:
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *    New test failure in master
>> CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=139506597706397620&branch=%3Cdefault%3E&tab=testDetails
>>  Changes may led to failure were done by         - ivandasch
>> http://ci.ignite.apache.org/viewModification.html?modId=825683&personal=false
>>
>>         - If your changes can led to this failure(s), please create issue
>> with label MakeTeamCityGreenAgain and assign it to you.
>>         -- If you have fix, please set ticket to PA state and write to
>> dev list fix is ready
>>         -- For case fix will require some time please mute test and set
>> label Muted_Test to issue
>>         - If you know which change caused failure please contact change
>> author directly
>>         - If you don't know which change caused failure please send
>> message to dev list to find out
>> Should you have any questions please contact [email protected] or write
>> to dev.list
>> Best Regards,
>> MTCGA.Bot
>> Notification generated at Tue Jul 17 02:06:49 MSK 2018
>>
>

Reply via email to