Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (nike.apache.org: domain of jmason@gmail.com designates
 209.85.218.217 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=FUXLtWebhThSzL8AdKLiBcl2DIv4lXHlU5E2TCvuYcGVD8CQUWTaizpY7kysGD/ycF
         AK7cESNURkpv1VGKSOup/bIo2+snKV5/8mJhnVjxcLpCuCBqYC0FpBPYW8iYlSlMfUE1
         sKM55abKuhbEi1U5oO5/kUMwcEYlMIZyNy1Sg=
MIME-Version: 1.0
Sender: jmason@gmail.com
In-Reply-To: <56FD3F59E2F64F0ABC1DD1D85CF850FF@developer>
References: <25aac9fc0906281900k495be2d5j40b1ad971dafba6d@mail.gmail.com>
	 <510143ac0906300537x44c6855q7cb58c6c103636ac@mail.gmail.com>
	 <25aac9fc0906300546q342ca863sf0ed1c7e49895456@mail.gmail.com>
	 <6c399e450906300617m351fad84q613b45b5bdfb7d96@mail.gmail.com>
	 <64CE30EF-DBE6-4C50-BF8F-DD7D8820DE32@apache.org>
	 <56FD3F59E2F64F0ABC1DD1D85CF850FF@developer>
Date: Mon, 6 Jul 2009 22:36:08 +0100
Message-ID: <6c399e450907061436u1d9f71f1y66fe80dfbb552b39@mail.gmail.com>
Subject: Re: Move builds off of Hudson master
From: Justin Mason <jm@jmason.org>
To: builds@apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 6, 2009 at 19:01, Gavin<gavin@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Nigel Daley [mailto:nigel@apache.org]
>> Sent: Friday, 3 July 2009 3:37 AM
>> To: builds@apache.org
>> Subject: Move builds off of Hudson master
>>
>> Folks,
>>
>> I'd really like to move builds off the Hudson master. =C2=A0Here's a
>> proposal:
>>
>> 1) We move the Hadoop related builds (Common, HDFS, Mapreduce, Pig,
>> ZooKeeper, Hive, HBase, Chukwa, Avro) off to some other machines (see
>> 4 below)
>>
>> 2) That would free up minerva and vesta as Ubuntu build slaves for all
>> the other projects (which should be more than enough capacity).
>>
>> 3) We get permission to use the current lucene.zones slave as a
>> Solaris build slave for those projects that really want a Solaris
>> build (how many is that I wonder?)
>>
>> 4) We add a bunch more Ubuntu slaves to hudson.zones out of a pool of
>> publicly IP'd yahoo.net machines my employer has for Hadoop related
>> builds.
>>
>> Thoughts?
>
> All sounds good to me, just do it I say.

+1.  I'd give it 72 hours from your initial post, and if there's no
-1's by then, consider it approved ;)

--j.

>> On Jun 30, 2009, at 6:17 AM, Justin Mason wrote:
>>
>> > On Tue, Jun 30, 2009 at 13:46, sebb<sebbaz@gmail.com> wrote:
>> >> On 30/06/2009, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>> >>> Hi,
>> >>>
>> >>> =C2=A0Another Tuscany-2x build [1] was stuck with lots of OOM errors=
 and
>> >>> =C2=A0other failures in the console log. I killed the build as it wa=
s
>> >>> taking
>> >>> =C2=A0already almost 7 hours, which is much more than the 40 minutes
>> >>> used by
>> >>> =C2=A0the last successful build.
>> >>>
>> >>> =C2=A0[1] http://hudson.zones.apache.org/hudson/job/Tuscany-2x/116/
>> >>
>> >> It looked to me as though the build was stalled, i.e. Hudson was not
>> >> able to detect/recover from the situation. Is this a known problem?
>> >>
>> >> Is there any way to give the builds a bit more memory?
>> >>
>> >> It looks like Tuscany has not built successfully for a long while, so
>> >> this is likely to keep happening.
>> >>
>> >> It's a pity that the console output does not have time-stamps, or it
>> >> would be a lot easier to tell that nothing was happening.
>> >
>> > It could be the entire machine was under memory pressure, given those
>> > OOM errors. =C2=A0I wonder if that caused the Hudson master to get
>> > confused.
>> >
>> > --j.
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.375 / Virus Database: 270.13.1/2211 - Release Date: 07/01/0=
9
>> 18:07:00
>
>