If other people are ignoring the results of the flakyTest target and that's the reason that people do not want to add FlakyTest category to tests that aren't currently marked with FlakyTest then here's my proposal... we delete FlakyTest category (well actually just rename it) and replace it with TestsThatFailMoreFrequentlyAndNeedToRunInFreshJVM category and we educate all geode developers to NOT ignore the results. If the test keeps failing when run in isolation under "TestsThatFailMoreFrequentlyAndNeedToRunInFreshJVM" then that means it needs to be fixed asap and not ignored. Thoughts?
On Wed, May 24, 2017 at 4:50 PM, Kirk Lund <kl...@apache.org> wrote: > Geode Nightly build is staying consistently RED... each night the tests > that fail vary some. Do we still want to not add FlakyTest category to > these tests and just live with a RED nightly build? > > What do you all want to do? Any ideas what to do to get it consistently > GREEN? > > The only way I know to get it GREEN is either a) we drop everything we're > working on and fix flaky tests or b) we add FlakyTest category to flaky > tests. The flakyTest target still runs the FlakyTest tests but it does so > with a fresh JVM. In my opinion we should NOT ignore the results of > flakyTest (and I personally do not ignore these results). I think it's a > useful way to run DUnit tests that have special needs. >
