Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALte62wt5qUUYMwZZrbuH8Z32CZjoXnyONJ8ZVGkCztS_6H=rQ@mail.gmail.com>
References: 
 <CAMUu0w_T1RCyYs3WiEY8Gh38WoRy8vWZOjC6mBSJ9r7TfuUbug@mail.gmail.com>
	<CA+RK=_D0YLKcedxd76mzPgRr6KaRG8GntQ6PBEQ=YVqvyxCX_A@mail.gmail.com>
	<CADcMMgH_K+LBX5Rf+EDeAJeNeAKU4LErCaS1+Z_7cWc0oCV7PQ@mail.gmail.com>
	<CA+RK=_C=1VVvDRtZmGVo9CsGzQxf=YPrVG3nFnEeqV+baFF6WQ@mail.gmail.com>
	<CAPQV63UoRzUkUO4YNKF5_N-VG5eQaeLa2Hq-Hme=eZJquLM=Lg@mail.gmail.com>
	<CALte62wt5qUUYMwZZrbuH8Z32CZjoXnyONJ8ZVGkCztS_6H=rQ@mail.gmail.com>
Date: Wed, 3 Apr 2013 07:53:20 -0700
Message-ID: 
 <CA+RK=_B1KiFNwpzcPB0QghGC_cQhp_OFrsM-uer6dVkmoEjpRw@mail.gmail.com>
Subject: Re: 0.95 and 0.96 remaining issues
From: Andrew Purtell <apurtell@apache.org>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=047d7b6dc6e2d32e5104d97603b1

--047d7b6dc6e2d32e5104d97603b1
Content-Type: text/plain; charset=ISO-8859-1

I only suggest a category to toggle on or off for flaky tests. Let's just
discuss that first. That seems easy to set up. Then we don't have to commit
changes just to run them on Jenkins.

The point here seems to be segregate flaky tests and fix them, not leave
them in a broken state, nor introduce weird "pass once in a while" new
criteria.

On Wednesday, April 3, 2013, Ted Yu wrote:

> Jean-Marc's idea is interesting.
> The tests in this 'flaky' category should succeed, say, once in 5
> consecutive builds.
> If particular test fails consistently after a checkin, we should
> investigate further.
>
>
> On Wed, Apr 3, 2013 at 4:38 AM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org <javascript:;>
> > wrote:
>
> > Or even always have them running in this new category but if one of
> > them fails,not tag the build as a fail? That way we can continue to
> > keep an eye on them but they are not turning the builds red?
> >
> > 2013/4/3 Andrew Purtell <apurtell@apache.org <javascript:;>>:
> > > Could we introduce a junit category for flakey tests such that they
> don't
> > > run unless we activate them with some flag to maven?
> > >
> > > On Tuesday, April 2, 2013, Stack wrote:
> > >
> > >> On Tue, Apr 2, 2013 at 6:20 PM, Andrew Purtell <apurtell@apache.org<javascript:;>
> > <javascript:;>>
> > >> wrote:
> > >>
> > >> > > - HBASE-7897 Add support for tags to Cell Interface
> > >> >
> > >> > I think one of us over here could pick this up, let me ask.
> > >> >
> > >> > > - Unit test fixes
> > >> >
> > >> > I have some stuff due by the 12th. After that I aim for green trunk
> > and
> > >> > 0.94 builds on 54.241.6.143, including the Hadoop 2 ones. Will put
> on
> > my
> > >> > hip boots.
> > >> >
> > >> >
> > >> I like Jimmy's suggestion from another thread where we just back out
> all
> > >> flakey tests and roll them in one at a time into a build that is
> usually
> > >> blue rather than always red so we can figure which tests and code
> > >> destabilize.
> > >>
> > >> St.Ack
> > >>
> > >
> > >
> > > --
> > > Best regards,
> > >
> > >    - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> >
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--047d7b6dc6e2d32e5104d97603b1--