[MTCGA]: new failures in builds [3766443] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: TC Bot triggers Run-All using a random JDK version

I can make builds autotag itself with used JDK. Also - from what JDKs does randomiser choose? > On 9 May 2019, at 12:56, Dmitriy Pavlov wrote: > > Hi Igniters, > > For your information, Apache Ignite TeamCity bot now triggers run all > (nightly) using some available JDK version (random each

[jira] [Created] (IGNITE-11842) clients fails to connect

James created IGNITE-11842: -- Summary: clients fails to connect Key: IGNITE-11842 URL: https://issues.apache.org/jira/browse/IGNITE-11842 Project: Ignite Issue Type: Bug Components: cache

[MTCGA]: new failures in builds [3669949, 3669948] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

TC Bot triggers Run-All using a random JDK version

Hi Igniters, For your information, Apache Ignite TeamCity bot now triggers run all (nightly) using some available JDK version (random each time). Used JDK is saved in the Bot DB and is shown at UI (see below). Next step could be changing the flakyness detection algorithm in the Bot to analyze

Re: Consistency check and fix (review request)

Hi Anton, Meanwhile can we extend a feature description from a user point of view? It would be good to provide some use cases when it can used. The thing that is yet understood by me is a conflict resolving. E.g. in systems inspired by Dynamo (sorry that no references, writing from phone)