hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Drob <md...@apache.org>
Subject Re: [DISCUSS] options for precommit test reliability?
Date Mon, 09 Oct 2017 20:21:27 GMT
+100

On Mon, Oct 9, 2017 at 3:13 PM, Andrew Purtell <apurtell@apache.org> wrote:

> Reasonable stable result once a day > unstable results at any frequency
>
> On Mon, Oct 9, 2017 at 12:51 PM, Sean Busbey <busbey@apache.org> wrote:
>
> > On Mon, Oct 9, 2017 at 1:23 PM, Andrew Purtell <apurtell@apache.org>
> > wrote:
> > > I find these options useful when running on contended or underpowered
> > test
> > > hosts
> > >
> > >     -Dsurefire.firstPartForkCount=1 \
> > >     -Dsurefire.secondPartForkCount=1 \
> > >     -Dsurefire.rerunFailingTestsCount=3
> > >
> > > It balloons the test suite execution time, but produces more stable
> > > results, and the rerun setting allows Surefire to help detect flaky
> > tests.
> > >
> >
> > These settings match what I do on underpowered hosts. I think it
> > usually takes ~6 hours to get through the test suite this way. Is
> > getting precommit feedback once a day prohibitively slow?
> >
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>    - A23, Crosstalk
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message