Hi Till, thank you for bringing this up. We really need to fix this.
Filing JIRAs with critical priority was how we tried to solve it in the past, but obviously it did not work. There seems to be a mismatch between assigned and actual priorities. As a first step, I would volunteer to gather a list of tests, which have failed in the last weeks and make sure that we have JIRAs for them. As a next step, we should coordinate how to resolve those issues (maybe prioritized by failure frequency) to get master stable again. – Ufuk On Wed, Apr 27, 2016 at 12:12 PM, Till Rohrmann <trohrm...@apache.org> wrote: > Hi Flink community, > > I just wanted to raise awareness that in the last 16 days there was just a > single Travis build of master which passed all tests. This indicates that > we have some serious problems with our test stability or even worse a > problem with the master itself. Having an unstable master makes it really > hard to assess whether new changes actually broke something or whether the > failing test was unrelated. > > We have currently 37 open issues labeled with test-stability and most of > them have a critical priority. Therefore, I would propose that we try to > tackle them as soon as possible in order to improve our testing stability. > > Cheers, > Till
