Hello Stanislav, Ignite also has some issues with Java 11 support. For a long time we have been ignoring Java 11 existence at all. At the moment, the community has been working on the full Java 11 support and this version should become a default one soon. The tests will be done for both Java 8 and Java 11.
I'll let Dmitry Pavlov dig into the details since he is the one who is driving or doing most of the adoption. - Denis On Tue, Feb 26, 2019 at 2:39 PM Stanislav Kozlovski < stanislav_kozlov...@outlook.com> wrote: > Hey there Ignite community, > > I contribute to a fellow open-source project - Apache Kafka - and there we > have been fighting flaky tests a lot. We run Java 8 and Java 11 builds on > every Pull Request and due to test flakiness, almost all of them turn out > red with 1 or 2 tests (completely unrelated to the change in the PR) > failing. This has resulted in committers either ignoring them and merging > the changes or in the worst case rerunning the hour-long build until it > becomes green. > This test flakiness has also slowed down our releases significantly. > > In general, I was just curious to understand if this is a problem that > your project faces as well. Does your project have a lot of intermittently > failing tests, do you have any active process of addressing such tests > (during the initial review, after realizing it is flaky, etc). Any pointers > will be greatly appreciated! > > Thanks, > Stanislav > > > <http://aka.ms/weboutlook> >
