Please don't mark Jetty9CachingClientServerTest as flaky. We need to look into why it failed and fix it. There are a bunch of other tests that are using the same framework, so marking this one test as flaky isn't going to help.
-Dan On Wed, Sep 13, 2017 at 10:07 AM, Jared Stewart <jstew...@pivotal.io> wrote: > I would prefer not to mark ExportLogsStatsOverHttpDUnitTest as flaky. > This is the first time we’ve seen it fail, and it looks like it failed due > to insufficient cleanup from a previous test. We’re working on finding the > culprit test and adding the missing cleanup. > > (Or you can mark it flaky for now, and we can unmark it as flaky when we > push a fix today/tomorrow.) > > - Jared > > > On Sep 13, 2017, at 9:34 AM, Kirk Lund <kl...@apache.org> wrote: > > > > We need to get more serious about getting the Geode Nightly Build back to > > consistent GREEN. > > > > I want to mark these flickering tests as FlakyTest. Please let me know if > > you have a problem with me doing so: > > > > 1) Jetty9CachingClientServerTest > > 2) ExportLogsStatsOverHttpDUnitTest > > > > If you do have a problem with marking these as FlakyTest, please suggest > > how we can get the build GREEN. > > > > Please remember that we are NOT supposed to ignore any test failures in > the > > flakyTest target. Any failures in that target should be prioritized for > > fixing and de-flickering ASAP. This is much better than marking such > tests > > with @Ignore. > > > > Thanks, > > Kirk > >
