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 nkeywal@gmail.com designates
 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+RK=_Bquh3_485E6hwg1dWmfR0=xvyCGRSiGw9CZEzpyvoe7A@mail.gmail.com>
References: 
 <CAPMERtj39v8OHeRzUHp7Yo2Ff81qz9nTzWr+p-kGcCuKbwQcfw@mail.gmail.com>
 <CA+RK=_Bquh3_485E6hwg1dWmfR0=xvyCGRSiGw9CZEzpyvoe7A@mail.gmail.com>
From: Nicolas Liochon <nkeywal@gmail.com>
Date: Wed, 27 Aug 2014 22:59:55 +0200
Message-ID: 
 <CAPcDmSsmgSX-9FfQFNk+v2T3Ga4eqKxKUE8tX48rV32NxEn0ag@mail.gmail.com>
Subject: Re: I wonder if it makes sense to restrict the HBase build to one
 build per jenkins host
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d043d66ddf4c79f0501a2b48d

--f46d043d66ddf4c79f0501a2b48d
Content-Type: text/plain; charset=UTF-8

It used to be the case for precommit builds: there was a single worker.
It's much simpler this way.
It seems it has changed, likely less than a year ago. I see on
https://builds.apache.org/computer/H0/load-statistics that there are 2
workers.
We're can't do what we want on these machines, as they are used by other
projects however. In the past, Giri was administrating these machines, I
don't know if it's still the case (Enis? Devaraj? Stack? Do you guys know?)

I guess that the root issue is that hdfs & other builds are not
parallelized as HBase are, so they need multiple workers to really use the
multiple cores of the build env...

Nicolas


On Wed, Aug 27, 2014 at 10:45 PM, Andrew Purtell <apurtell@apache.org>
wrote:

> +1, if it's possible on ASF Jenkins
>
> We also share with other projects. I've seen build reports implicating
> Oozie tests for supposed HBase test zombies.
>
> When we had cloud based Jenkins running at Trend Micro and Intel we
> launched instances on demand as we needed workers, but never more than one
> worker per instance concurrently. Definitely helps to reduce failures due
> to unexpected state from interactions between tests.
>
>
> On Wed, Aug 27, 2014 at 1:28 PM, Alex Newman <posix4e@gmail.com> wrote:
>
> > I have noticed that HBase tests can cause a good deal of inherent test
> > interference. We have had much better luck running one and only one
> > set of the tests at a time. I notice that this currently is not
> > happening. I don't have any rights on jenkins, so perhaps someone else
> > could give this a shot. I'd be glad to describe how do it. Another
> > option would be to run the build from within a container (We do this
> > at WanDISCO). Finally I got the build running on travis ci.  Checkout
> > https://github.com/OhmData/hbase-public/tree/travis for an example of
> > how to get this done.
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

--f46d043d66ddf4c79f0501a2b48d--