Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90097
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)
MIME-Version: 1.0
In-Reply-To: <CABBJUpcFwscEst8iK6eFsWgqob8+wa3xw7-_QwvC+4zZQc6A5A@mail.gmail.com>
References: <89.85.51216.3FD44865@pb1.pair.com>
	<C1CB595D-BFCB-4B60-9BC3-935BB280FA0B@php.net>
	<CABBJUpcFwscEst8iK6eFsWgqob8+wa3xw7-_QwvC+4zZQc6A5A@mail.gmail.com>
Date: Tue, 5 Jan 2016 16:03:52 +0100
Message-ID: <CAH-PCH7uxDTLkzfu-U7hior00ecKm9woFhgpj924nhhWVfFy5w@mail.gmail.com>
To: Xinchen Hui <laruence@php.net>
Cc: Michael Wallner <mike@php.net>, Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114435f4b649e20528978b76
Subject: Re: [PHP-DEV] What's up with gcov.php.net?
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a114435f4b649e20528978b76
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 31, 2015 at 10:26 AM, Xinchen Hui <laruence@php.net> wrote:

> Hey:
>
>
> On Thu, Dec 31, 2015 at 5:19 PM, Michael Wallner <mike@php.net> wrote:
>
> >
> > > On 30 12 2015, at 22:34, Andrea Faulds <ajf@ajf.me> wrote:
> > >
> > > Hi everyone,
> > >
> > > 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 se=
en
> > much more reasonable numbers (i.e. usually zero).
> >
> > A guess might be, that many of the tests run on gcov are disabled on
> > travis.
> >
> > >
> > > 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, an=
d
> > secondly, since we use Travis for continuous integration these days, wh=
y
> is
> > the box even still running?
> >
> > gcov is about coverage too, so=E2=80=A6
> >
> and also valgrind, which is quite useful, since it takes too long to run =
in
> laptop.
>
> thanks
>
>
which is also explains some of the differences between the test failures,
running the testsuite with valgrind can find much more memory leaks
compared to the simple run-tests run on travis


--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a114435f4b649e20528978b76--