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 saint.ack@gmail.com designates
 209.85.214.48 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAPcDmSuH++sdSC=9dcKwiMmRxq36E8quZTcRu3FA=nKyc5=3Vg@mail.gmail.com>
References: 
 <CAPcDmSuH++sdSC=9dcKwiMmRxq36E8quZTcRu3FA=nKyc5=3Vg@mail.gmail.com>
Date: Wed, 10 Apr 2013 13:01:04 -0700
Message-ID: 
 <CADcMMgEHZr2OD_aCtFs737TDa98LomCDmO4wOachMiaHmWeptA@mail.gmail.com>
Subject: Re: trunk build
From: Stack <stack@duboce.net>
To: HBase Dev List <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=f46d040f9dc846d96404da07218d

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

On Wed, Apr 10, 2013 at 12:17 PM, Nicolas Liochon <nkeywal@gmail.com> wrote:

> Issues were:
>  - Trunk built on ubuntu* machines where using jdk 1.7 while the precommit,
> on hadoop*, was on 1.6
>  - precommit can't be set to use 1.7. It uses 1.6 32bits, as set by
> hudsonEnv.sh
>  - Trunk builds are executed in parallel with other builds, while for
> precommit, hbase is alone on is machine.
>  - jenkins, on precommit, often fails to parse the build results (jenkins
> memory issue, still open, see below).
>
> I've:
>  - changed the jdk to 1.6
>  - set the test parallelisation to 2 on trunk/ubuntu
>  - fixed various test flakiness
>  - increased the test timeout of a few tests to 60s. We should not set the
> timeout to lower values, it makes them dependant to the machine env. When
> in doubt, don't use them imho, or set them to 10 minutes or more.
>  - changes some logs from debug to trace or even remove some.
>
> Still to be done:
>  - install the jdk 1.7 64 bits on the hadoop* machines. Someone knows how
> to do that?
>  - find a way to make it used by the test even if we use the script
> 'hudsonEnv.sh'.
>  - increase the memory of the Jenkins JVM. Again, someone knows how to do
> that?
>  - use all the hadoop* to build. We're using 3 out of the 9 available
> today. Any reason for this?
>  - there are still some flaky tests...
>

I asked the above questions of infrastructure:
https://issues.apache.org/jira/browse/INFRA-6140

Thanks for doing above detective work N.

St.Ack

--f46d040f9dc846d96404da07218d--