On Thu, Dec 31, 2015 at 10:26 AM, Xinchen Hui <larue...@php.net> wrote:
> Hey: > > > On Thu, Dec 31, 2015 at 5:19 PM, Michael Wallner <m...@php.net> wrote: > > > > > > On 30 12 2015, at 22:34, Andrea Faulds <a...@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 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. > > > > > > > > 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… > > > 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 -- Ferenc Kovács @Tyr43l - http://tyrael.hu
