Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89936
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
Sender: Michael Wallner <mike.php.net@gmail.com>
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
In-Reply-To: <89.85.51216.3FD44865@pb1.pair.com>
Date: Thu, 31 Dec 2015 10:19:17 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <C1CB595D-BFCB-4B60-9BC3-935BB280FA0B@php.net>
References: <89.85.51216.3FD44865@pb1.pair.com>
To: Andrea Faulds <ajf@ajf.me>
Subject: Re: [PHP-DEV] What's up with gcov.php.net?
From: mike@php.net (Michael Wallner)


> On 30 12 2015, at 22:34, Andrea Faulds <ajf@ajf.me> wrote:
>=20
> Hi everyone,
>=20
> If any of you have looked at http://gcov.php.net any time in the last =
three years, you'll probably have noticed an alarming and inexplicably =
high number of test failures. And if you've looked at Travis, you'll =
have seen much more reasonable numbers (i.e. usually zero).

A guess might be, that many of the tests run on gcov are disabled on =
travis.=20

>=20
> So, I'd like to ask, why does gcov.php.net always show such high =
numbers, and apparently has things that are fixed show up as broken, and =
secondly, since we use Travis for continuous integration these days, why =
is the box even still running?

gcov is about coverage too, so=85

Anyway, you=92ve probably got to talk to Nuno; IIRC he was/is managing =
the gcov box.

Cheers,
Mike