Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54741 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91053 invoked from network); 20 Aug 2011 08:25:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Aug 2011 08:25:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.170 mail-gx0-f170.google.com Received: from [209.85.161.170] ([209.85.161.170:53103] helo=mail-gx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 05/32-05787-98F6F4E4 for ; Sat, 20 Aug 2011 04:25:46 -0400 Received: by gxk27 with SMTP id 27so3284201gxk.29 for ; Sat, 20 Aug 2011 01:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3tRof1h+UJNlamkPNBongSenbEnuNbGdDh7TyneYaIg=; b=D/FbkWIBumEMuxaYxdhw4dXAnMzSmkpbJBamuMGI03WxN0QW96LO7KV9isaQQZJR9k h2eI1re7u4xtlfMxBGqbWQaHYUHr44DfvR1zpcv0b93qJrbbjbih6kHmvSh6bSJ5sJwo fOEb2s5+Fgc5IkW3v07VneraBD18Khj0gKRog= MIME-Version: 1.0 Received: by 10.236.191.136 with SMTP id g8mr1653155yhn.5.1313828742151; Sat, 20 Aug 2011 01:25:42 -0700 (PDT) Received: by 10.147.41.9 with HTTP; Sat, 20 Aug 2011 01:25:42 -0700 (PDT) In-Reply-To: <4E4EFB43.1050201@sugarcrm.com> References: <4E4EEED3.4070001@sugarcrm.com> <4E4EF9AE.6090102@lerdorf.com> <4E4EFB43.1050201@sugarcrm.com> Date: Sat, 20 Aug 2011 10:25:42 +0200 Message-ID: To: Stas Malyshev Cc: Rasmus Lerdorf , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] Test failures (was: 5.3.7pl1) From: pierre.php@gmail.com (Pierre Joye) hi, Right, I sadly did not run them as I use to between the last RC and final but only the apps tests (wp&co), which do not use crypt's md5. I also agree about the amount of failing tests and warnings, for the same reasons. However checking the delta between two releases should help too (that's what I use to stop a release). btw, can we go with 5.3.8 instead? I really don't like the pl thing :) Cheers, On Sat, Aug 20, 2011 at 2:09 AM, Stas Malyshev wrote: > Hi! > > On 8/19/11 5:02 PM, Rasmus Lerdorf wrote: >> >> The secondary problem is that we are not doing a good job running our >> tests prior to releases. I think this is mostly because we have way too >> many tests that fail and one more or less failing test gets lost in the >> noise. > > Yes, this is a problem: here > http://gcov.php.net/viewer.php?version=PHP_5_4&func=tests we have 218 > failing tests. Unit test system with this amount of failures is next to > useless. So if we have some component that is buggy (like DateTime) or not > updated - we need to figure out a way to separate tests that we know would > fail (XFAIL?) from tests that should not fail and not release a version > until the second number is 0. Otherwise we get broken releases. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org