Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 57637 invoked from network); 29 Nov 2006 09:22:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Nov 2006 09:22:55 -0000 Received: (qmail 14787 invoked by uid 500); 29 Nov 2006 09:23:01 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 14747 invoked by uid 500); 29 Nov 2006 09:23:01 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 14738 invoked by uid 99); 29 Nov 2006 09:23:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Nov 2006 01:23:01 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of t.p.ellison@gmail.com designates 64.233.182.187 as permitted sender) Received: from [64.233.182.187] (HELO nf-out-0910.google.com) (64.233.182.187) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Nov 2006 01:22:49 -0800 Received: by nf-out-0910.google.com with SMTP id a4so2909060nfc for ; Wed, 29 Nov 2006 01:22:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=gMzZ5ubKtdDv9sAjjRN8LOEhIagaoxqQ/RFHru8z1YW9PcnZe2ZaPY4M89qIjfcg6GNtVYe2o2iNk3e3lYTPMeSCnqlW3P1sZ4i01hY35vjDMEBkqV9aGwb/HiEt6hrYA0DEatDl7rpZSnOmTjyD7CyP5qnypkFumEiKLvDJtzY= Received: by 10.49.21.8 with SMTP id y8mr5920863nfi.1164792148160; Wed, 29 Nov 2006 01:22:28 -0800 (PST) Received: from ?192.168.0.6? ( [86.111.176.100]) by mx.google.com with ESMTP id y24sm27257449nfb.2006.11.29.01.22.27; Wed, 29 Nov 2006 01:22:27 -0800 (PST) Message-ID: <456D514C.1020402@gmail.com> Date: Wed, 29 Nov 2006 09:22:20 +0000 From: Tim Ellison User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: dev@harmony.apache.org Subject: Re: [general] Can we stop commits when the build is broken? References: <906dd82e0611282315h4db5e446hd1a38ed558cb7d14@mail.gmail.com> In-Reply-To: <906dd82e0611282315h4db5e446hd1a38ed558cb7d14@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mikhail Loenko wrote: > Today I've counted 12 commits after the first failure notification came. > > Can we avoid that? +1 -- it is important that we retain stability. When the build is broken please stop putting in new code and go see why. FYI: the classlib build on IBM VM status is: - win32 is ok, but the build machine needs maintenance so is offline for a short time. Local build/test on another WinXP machine is working for me. - linux32 is failing on the build machine because it cannot load the Xtst libraries. Plan to install them shortly and then that build will pass. Local build/test on a different machine with libs is working for me. Regards, Tim -- Tim Ellison (t.p.ellison@gmail.com) IBM Java technology centre, UK.