Yes, it seems I need to do some update to
https://github.com/dspavlov/ignite-teamcity-helper to reset fail rate after
reasonable timeout/runs of tests.
I quess 3 weeks and/or 100 successfull runs may be sufficient to consider
test as fixed. WDYT?
ср, 7 мар. 2018 г. в 15:02, Pavel Tupitsyn :
> Ye
Yep, this test is not flaky at all, it had failed before for the same exact
reason, forgetting to update .NET.
On Wed, Mar 7, 2018 at 12:13 PM, Dmitry Pavlov
wrote:
> Hi Pavel,
>
> Thank you for pointing to this issue. We have detected it under Teamcity
> monitoring, but still any additional inf
Hi Pavel,
Thank you for pointing to this issue. We have detected it under Teamcity
monitoring, but still any additional info on test failures is appreciated.
I've checked PR run but did not noticed this failures, I have considered
this failures as flaky:
Ignite Platform .NET Core Linux [ test
Igniters, Alexey G, Pavel K,
IGNITE-6113 changes [1] caused broken .NET test [2]
Have you run TeamCity before merging?
Please fix this.
When new APIs are added to Java you should:
a) add them to .NET as well
- or -
b) file a ticket and update .NET test (see how in CacheParityTest.cs we
have a bu
