hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: [DISCUSS] getting postcommit tests back to green.
Date Wed, 30 Sep 2015 18:52:07 GMT
We're looking at sponsoring EC2 or Heroku based resources. Agree,
additional datapoints can help. It would be a Jenkins based setup so we
could run precommit builds on it. Hopefully we can come back with good news.


On Wed, Sep 30, 2015 at 11:43 AM, Stack <stack@duboce.net> wrote:

> On Tue, Sep 29, 2015 at 8:06 PM, Sean Busbey <busbey@cloudera.com> wrote:
>
> > Hi Folks!
> >
> > Recently our postcommit tests have been in the pits. Essentially we've
> > been broken since mid to late August[1]. While Stack's been fighting
> > the good fight, I think things are far enough gone that we need to
> > consider more drastic measures.
> >
> > I've been playing with getting things going on Travis-CI. It might be
> > a good stop-gap measure while we wait for ASF Infra to get some
> > additional testing resources. I believe Spark uses it already. It
> > won't help with precommit unless we shift to github PRs (which I'd
> > prefer not to do).
> >
> > Anyone have any other ideas or concerns?
> >
> >
> Having another (public) build to compare apache postcommit to is great
> Sean. Another datapoint on our build state will help with fixup.
> St.Ack
>
>
>
> >
> > [1] ref:
> > https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK/
> > https://builds.apache.org/job/HBase-1.3/
> >
> > --
> > Sean
> >
>



-- 
Best regards,

   - Andy

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

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