Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74761 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15651 invoked from network); 5 Jun 2014 19:10:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2014 19:10:54 -0000 Authentication-Results: pb1.pair.com header.from=nicolai.scheer@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=nicolai.scheer@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender) X-PHP-List-Original-Sender: nicolai.scheer@gmail.com X-Host-Fingerprint: 209.85.213.42 mail-yh0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:49269] helo=mail-yh0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/00-14942-CB0C0935 for ; Thu, 05 Jun 2014 15:10:53 -0400 Received: by mail-yh0-f42.google.com with SMTP id i57so252293yha.15 for ; Thu, 05 Jun 2014 12:10:50 -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=7bZDtxqoxxyN5QCmC7mKWlu/WP+klClni4AAxMckk38=; b=bOPJ6FC1wLXc8SyzdW4vDJsCl/DHTEJbfUaWyvaOcZg5qnIMwR06/kKdlp6YAld1/a YVaETWtjlcLFbCERXgWVoxi/hkTqr8Wyxpg2JeL8Y5o2d6Zg/9qgZq8ezUmzhokh0pQI BJIBNjghkfo0K6HcTHyIC/k8Ng5Pxkk1Qa1e3eW+az60AuDlf4vu4vgy+qdFBcA1fWzo gGJoRLFyECZ15RKcVkpbt2HrCwdTIIfNuNF0tfDAIJserJfvKWKpggLtW2vOPu/8/DPQ zzHdydb5BI9j5EqFST8hxLu6JCyD3Ab6UbLCHIgP94LzJdO4met/dP26A8m6DtsMEZVQ v09w== MIME-Version: 1.0 X-Received: by 10.236.228.40 with SMTP id e38mr87391017yhq.76.1401995449749; Thu, 05 Jun 2014 12:10:49 -0700 (PDT) Received: by 10.170.88.215 with HTTP; Thu, 5 Jun 2014 12:10:49 -0700 (PDT) In-Reply-To: <8305622955BF49F18659A0CACD51E1DA@pc07654> References: <8305622955BF49F18659A0CACD51E1DA@pc07654> Date: Thu, 5 Jun 2014 21:10:49 +0200 Message-ID: To: Nuno Lopes Cc: Ferenc Kovacs , PHP Internals Content-Type: multipart/alternative; boundary=001a11c2c4dac254cc04fb1b805b Subject: Re: [PHP-DEV] tests code coverage for php 5.5 From: nicolai.scheer@gmail.com (Nicolai Scheer) --001a11c2c4dac254cc04fb1b805b Content-Type: text/plain; charset=UTF-8 Hi! On 5 June 2014 20:08, Nuno Lopes wrote: > Hi, >>> >>> looking for tasks to invest a little spare time in the weeks to come I >>> had >>> a look at >>> >>> http://gcov.php.net/viewer.php?version=PHP_5_5 >>> >>> The test coverage is suspiciously low... >>> >>> Test coverage of 5.4 is quite high, so is coverage for 5.3. >>> >>> I would have guessed, that for a new major php version all tests from the >>> previous version are reused, and fixed if needed. >>> >>> Looking at the 5.5 source tree all the phpt files seem in place... Aren't >>> the tests just currently not executed on gcov.php.net? >>> >>> Thanks for any insight! >>> >>> Greetings >>> >>> Nico >>> >>> >> Yeah, something is definitely wrong: >> http://gcov.php.net/PHP_5_4/lcov_html/ >> vs >> http://gcov.php.net/PHP_5_5/lcov_html/ >> >> and it we dates are correct, the last gcov build for 5.6 was more than a >> week ago: >> http://gcov.php.net/ >> http://gcov.php.net/PHP_5_6/lcov_html/ >> >> ps: I've cc'ed Nuno as he is the man who knows our gcov setup. >> > > Thanks for CC'ing me. > > Short version: the problem is fixed. The next round of builds will have > correct coverage data (including PHP_HEAD that will be available within a > few hours). > > Long version: There was a bug in the makefile that was triggered when the > Zend opcode cache was commited. A few days ago I tried to fix it, but > ended up introducing another bug. Anyway, I believe my last commit fixed > the problem in Makefile.gcov, and therefore the next round of builds should > finally have correct data. > > Nuno > > P.S.: BTW, regarding the existence of gcov.php.net, when it was created > there were no off-the-shelf solutions, and therefore we created our own. > It's not awsome, but works fine. Of course I'm fine with killing it when a > replacement becomes available. > Thanks for looking into this issue and resolving it :) Looking forward to checking the results. Greetings Nico --001a11c2c4dac254cc04fb1b805b--