Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 22359 invoked from network); 25 May 2010 00:17:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 May 2010 00:17:43 -0000 Received: (qmail 52866 invoked by uid 500); 25 May 2010 00:17:43 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 52818 invoked by uid 500); 25 May 2010 00:17:42 -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 52809 invoked by uid 99); 25 May 2010 00:17:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 May 2010 00:17:42 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nbeyer@gmail.com designates 209.85.161.49 as permitted sender) Received: from [209.85.161.49] (HELO mail-fx0-f49.google.com) (209.85.161.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 May 2010 00:17:35 +0000 Received: by fxm15 with SMTP id 15so2967845fxm.36 for ; Mon, 24 May 2010 17:17:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=NIf5ARA1npStAhHGkgHULJTT1Fb1zJL5kEWp0L8Lujk=; b=ObyNR1mJHIDEu5dFYR6TfShq9bxng1pnC7zWGWyXQODA9YmYgz0ewYrY8tH6oK50FE NkUlZ4PFYGOoAV83F69qKfx9tvkq1tJKFEYF7wAEXaLatYTfay3tL8Z5cs0Tzynk7YFZ p3Bh6TQz3Pbc/M9bhxkBaRMpQg+7TGinrnFYc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=rOTW8jEsybZFXvJlBc8zfmdz1sCeZsLJDBjL9CC1+bSwtonL1jcsjvCgoAddqaHlwK QrPXBCgVRYfbypFfidCwlMH77W8vckzwx5g7SzpnLlcUkx2tZV4YZflf/myxCYBvsPy+ A0IF5a4LLILmEE4UkdmIeSJ7pgNjLyqcLyMCw= MIME-Version: 1.0 Received: by 10.103.79.19 with SMTP id g19mr4591943mul.75.1274746634767; Mon, 24 May 2010 17:17:14 -0700 (PDT) Sender: nbeyer@gmail.com Received: by 10.102.253.2 with HTTP; Mon, 24 May 2010 17:17:14 -0700 (PDT) Date: Mon, 24 May 2010 19:17:14 -0500 X-Google-Sender-Auth: 9EUq5fv162LKQfq9Kvk9jq10E4c Message-ID: Subject: [proposal] For future milestones, expect zero test failures From: Nathan Beyer To: dev@harmony.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org For future milestone votes, I'd like to propose that we set the expectation of zero test failures. Every time we do a milestone and I run the build and tests I find myself looking at the test failures (there are ALWAYS failures) and ask 'are these expected'? If the failures are expected, they should be excluded and the tests should just pass. If this proposal is workable, immediately after this upcoming release, all 'expected' failures will be pulled into the exclusion lists. -Nathan