Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59304 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15208 invoked from network); 1 Apr 2012 15:13:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2012 15:13:19 -0000 Authentication-Results: pb1.pair.com header.from=confik@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=confik@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender) X-PHP-List-Original-Sender: confik@gmail.com X-Host-Fingerprint: 209.85.213.170 mail-yx0-f170.google.com Received: from [209.85.213.170] ([209.85.213.170:52181] helo=mail-yx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/02-01129-E80787F4 for ; Sun, 01 Apr 2012 11:13:18 -0400 Received: by yenl5 with SMTP id l5so1064553yen.29 for ; Sun, 01 Apr 2012 08:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XYA42wHxIHX5K4PYfKrFmJpz7HYoyIHLow7WO56Rmc0=; b=WMvPhNpFBRwNHEPykp0zWo6cF6RNtQqs7k4HJPWij26nI+nBy3fyMNt/d1x8+8RIdY H0ljgs8Z5izygPr3P9X7+4mQO98f4T5deBjtuz0VrJ2Hf8OulFdj+bcMjtb07OeVf4b6 SnRy8Axvif7apmDVnb/unGoGJLuE6aDBe1zlt2JEUWs3xZsy93Qou1IIexnzvENZxwnv aqYBFXjNmIJBOdtGhkcQpvWm465XkYvNtmwomOYP7x5u6DGSezEMS4drjv6s2uHhrV3o x1CXhV0VNwOJ1IbIfg1asbHY6BdMsdMHQLuRa9dumeQugY+tlnGDODSsh5hQSsfHxubH L5MA== MIME-Version: 1.0 Received: by 10.236.161.73 with SMTP id v49mr4198181yhk.89.1333293195858; Sun, 01 Apr 2012 08:13:15 -0700 (PDT) Received: by 10.101.213.40 with HTTP; Sun, 1 Apr 2012 08:13:15 -0700 (PDT) In-Reply-To: References: <4F75EA77.3010300@oracle.com> <4F76B73B.2060005@sugarcrm.com> <1333222079.9243.3864.camel@guybrush> Date: Sun, 1 Apr 2012 20:13:15 +0500 Message-ID: To: Ferenc Kovacs Cc: Christopher Jones , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=20cf302d4c5c5212b404bc9f83a7 Subject: Change all XFAIL tests to FAIL From: confik@gmail.com (Alexey Shein) --20cf302d4c5c5212b404bc9f83a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 1 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3. 14:27 =D0=BF=D0=BE=D0= =BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C Ferenc Kovacs > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > On Sun, Apr 1, 2012 at 9:39 AM, Christopher Jones < > christopher.jones@oracle.com > wrote: > >> >> >> On 3/31/12 2:38 PM, Alexey Shein wrote: >> >>> 1 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3. 0:27 =D0=BF=D0=BE= =D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C Johannes Schl= =C3=BCter >>> > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81= =D0=B0=D0=BB: >>> >>>> On Sat, 2012-03-31 at 13:21 +0500, Alexey Shein wrote: >>>> >>>>> By constantly publishing >>>>> newsletter with failed / xfail bugs you're telling them "That's our >>>>> current problems. Maybe you could help us with them". This way we >>>>> could convert that discussing energy into some good patches. >>>>> >>>> >>>> While many people will simply filter them out. At least that's my >>>> experience with such automated mails in different projects ;-) >>>> >>>> johannes >>>> >>> >>> Okay, let's find it out. I've created a poll here: >>> https://wiki.php.net/xfail_**poll . >>> Please, leave your voice. I'll close the poll in a week. Thank you. >>> >>> >> Is there anything in the Jenkins work that makes this discussion irrelevant >> (or more relevant)? What other ways should we be running & reviewing tes= t >> failures? >> >> > currently XFAILs are handled as passing tests. > I'm working on a solution for having email notifications about new test > failures. Wow, that was great post :) > snip > you can also see a single test result history via selecting a test and > clicking on the History link ( > http://ci.qa.php.net/job/php-src-5.4-matrix-build/651/architecture=3Dx86,os= =3Dlinux-debian-6.0/testReport/php-src.ext.libxml/tests/004_phpt___libxml_s= et_streams_context__/history/ ? > for > example) here you can also see the status for that test in each build, so > you can see when was that introduced or fixed. > for example you can see that the libxml_set_streams_context() started > failing after build number 641, where you can see the Changes mentions a > libxml bugfix: > http://ci.qa.php.net/job/php-src-5.4-matrix-build/architecture=3Dx86,os=3Dl= inux-debian-6.0/641/changes The one problem I see here is that we keep only 100 last builds, so if bug is old enough you can't know build/revision where it's introduced. Maybe we should not keep in jenkins build php binary but only lightweight stuff like junit logs, coverage reports (if we have them) and etc. This way build size become smaller, so we can keep more of them. -- Regards, Shein Alexey --=20 Regards, Shein Alexey --20cf302d4c5c5212b404bc9f83a7--