Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54065 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84651 invoked from network); 18 Jul 2011 23:44:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2011 23:44:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=felipensp@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=felipensp@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.46 as permitted sender) X-PHP-List-Original-Sender: felipensp@gmail.com X-Host-Fingerprint: 209.85.210.46 mail-pz0-f46.google.com Received: from [209.85.210.46] ([209.85.210.46:49791] helo=mail-pz0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CF/E4-57459-445C42E4 for ; Mon, 18 Jul 2011 19:44:05 -0400 Received: by pzk3 with SMTP id 3so4544171pzk.33 for ; Mon, 18 Jul 2011 16:44:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=duRIZriOs5glL//Bb4sTeeDU1KnpUtty4UVfEKmEJMQ=; b=JOoa7J9KOJjbGwgmq5P7SAjf4kbqFHIjL2VdlveicvikWsbkqSLIygPBeF7/HJNWFc 9n9lPktdNRSSQlTz+wPt2ykI08sU7XBJ655bZ4Lbcft3q0GdCNwjiqNVE4bcLkwNeb72 gN6hK/AXn9AuRH8IhVHpvUvHR+wi59OKiHGMI= Received: by 10.142.131.20 with SMTP id e20mr3199387wfd.211.1311032642099; Mon, 18 Jul 2011 16:44:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.187.9 with HTTP; Mon, 18 Jul 2011 16:43:42 -0700 (PDT) In-Reply-To: <4E24C26D.7040409@sugarcrm.com> References: <4E24C26D.7040409@sugarcrm.com> Date: Mon, 18 Jul 2011 20:43:42 -0300 Message-ID: To: Stas Malyshev Cc: Nuno Lopes , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] is gcov.php.net still useful? From: felipensp@gmail.com (Felipe Pena) 2011/7/18 Stas Malyshev : > Hi! > >> The gcov.php.net machine is about to die. Nexcess (the owner) already >> offered us the possibility to get a replacement. >> However, before accepting their offer I would like to know if someone is >> still using the gcov.php.net service. Is it still useful for anyone? > > I think test coverage, valgrind and failures report are useful, especially > that we're nearing 5.4 release. The latter probably we could also get from > QA reports, but others probably not - like coverage, valgrind, parameters > etc. reports. > > BTW parameters report needs to be updated - it doesn't know about new 'p' > parameter. > It already was updated, but wasn't synced with svn. And I used to read the test failures and valgrind logs on gcov as well. -- Regards, Felipe Pena