Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of ndimiduk@gmail.com designates
 209.85.223.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAB5sDN+k9tde1nrVmLY4328ZAPzzPy+oO9fDBGDsXB-uix_H2g@mail.gmail.com>
References: <1356465472.90009.YahooMailNeo@web140605.mail.bf1.yahoo.com>
 <CADcMMgGNuJk1isZrr77cE0h3ona=zQAUGHN=1PQEH-pTU_u_Vw@mail.gmail.com>
 <CADcMMgFh=NqY_k0Pj75oVpdc2=J6VqPWaGzUuVVVcV-4jVBHoQ@mail.gmail.com>
 <CADcMMgEx+nzBnrm_4nW2EeZX=_LyaLbsb0uyRFtkSj0DGhfj6Q@mail.gmail.com>
 <CAMUu0w98P57fVs+pK1Dn-XZXssL4HNLbncgoJhb3McrJn-WNog@mail.gmail.com>
 <CA+RK=_AsobJ8qff17YRy_WQqkh9qQqKxnygLhW1JornVB-F0zg@mail.gmail.com>
 <1356590270.31822.YahooMailNeo@web140606.mail.bf1.yahoo.com>
 <CAMUu0w9GxeM2pXkiVzWk+5pJ2hc2UbC+rvhwm_xxNPuuQdCjzg@mail.gmail.com>
 <CALte62yvtHJZkXbEpzMU0hFov3_395tCVdQ-+QV1zrTb7VTDZw@mail.gmail.com>
 <1356741275.77005.YahooMailNeo@web140603.mail.bf1.yahoo.com>
 <CAB5sDN+k9tde1nrVmLY4328ZAPzzPy+oO9fDBGDsXB-uix_H2g@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Thu, 10 Jan 2013 14:20:36 -0800
Message-ID: 
 <CANZa=GuEbXA9d4-H6CdsJ24Hg+3g653xGu=SELBD464Ge9WHcw@mail.gmail.com>
Subject: Re: 0.94 tests back in shape and some guidelines
To: dev@hbase.apache.org
Cc: Jesse Yates <jesse.k.yates@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f3b9f49ba2eb004d2f69720

--e89a8f3b9f49ba2eb004d2f69720
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 29, 2012 at 11:45 AM, Jesse Yates <jesse.k.yates@gmail.com>wrot=
e:

> Something like a -P jenkins? It would also put source control on how we r=
un
> the test/build CI.
>
> Happy do put up a quick patch, if people are interested.
>

Yes, please! A corresponding update to the docbook would be excellent as
well ;)

-n

 On Fri, Dec 28, 2012 at 4:34 PM, lars hofhansl <lhofhansl@yahoo.com> wrote=
:
>
> > I feel that would be overkill. Test suite runs for a long time.
> Personally
> > I hate to run them locally and have my machine taken over for an hour.
> >
> > If is passed HadoopQA in trunk and a few relevant tests in 0.94 were ru=
n
> > (if applicable) I think that is good enough.
> >
> > If it doesn't pass the 0.94 run we'll find out soon enough. If the test
> > suite is stable that is :)
> >
> >
> > The gatekeeper are the release tests, not HadoopQA... IMHO.
> >
> >
> > -- Lars
> >
> >
> >
> > ________________________________
> >  From: Ted Yu <yuzhihong@gmail.com>
> > To: dev@hbase.apache.org
> > Cc: lars hofhansl <lhofhansl@yahoo.com>
> > Sent: Friday, December 28, 2012 4:28 PM
> > Subject: Re: 0.94 tests back in shape and some guidelines
> >
> > Since we don't have Hadoop QA for 0.94 patches yet, does it make sense
> for
> > either contributor (patch owner) or the committer who plans to integrat=
e
> > the patch to present test suite result before integration ?
> >
> > There is subtle difference between 0.94 and trunk which may lead to
> > unexpected results.
> >
> > Cheers
> >
> > On Thu, Dec 27, 2012 at 11:26 AM, Enis S=C3=B6ztutar <enis.soz@gmail.co=
m>
> > wrote:
> >
> > > I think it is not a matter of running the tests N times, but more so =
on
> > > running different platforms. From our builds, what we see most often =
is
> > > that the test runs just fine under CentOS 6, but becomes more flaky
> under
> > > CentOS 5 possibly b/c of thread scheduling differences. Moreover, und=
er
> > > windows, the threads are not immediately scheduled to run after start=
()
> > > which causes further race conditions which does not occur so frequent=
ly
> > > under *nix systems.
> > >
> > > For 0.94 QA, theoretically we should not this. However in practice I
> see
> > > that if there is a brave soul to work on it, we will find it useful.
> > >
> > > Enis
> > >
> > > On Wed, Dec 26, 2012 at 10:37 PM, lars hofhansl <lhofhansl@yahoo.com>
> > > wrote:
> > >
> > > > If we make it too onerous we'll see fewer contributions especially =
in
> > the
> > > > test area. :)
> > > >
> > >
> >
>

--e89a8f3b9f49ba2eb004d2f69720--