I am current maintainer of gcov server, I planned this kind of integration
with azure, so once again, thanks.
+1 to ditching gcov.php.net, we are terrible at infra ...
On Mon, 14 Oct 2019, 16:13 Nikita Popov, wrote:
> On Mon, Sep 30, 2019 at 2:30 PM Gerard Roche
> wrote:
>
> > > gcov.php.net u
On Mon, Sep 30, 2019 at 2:30 PM Gerard Roche
wrote:
> > gcov.php.net used to provide valgrind reports and code coverage for
> > php-src. It no longer works with 7.4/8.0, because the OS is very old, and
> > building new versions of PHP there gets very hard. The valgrind reports
> > have essentiall
On 30.09.2019 at 14:32, Gerard Roche wrote:
>> gcov.php.net used to provide valgrind reports and code coverage for
>> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
>> building new versions of PHP there gets very hard. The valgrind reports
>> have essentially been subsum
> gcov.php.net used to provide valgrind reports and code coverage for
> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
> building new versions of PHP there gets very hard. The valgrind reports
> have essentially been subsumed by asan/ubsan on Azure Pipelines, but we're
>
On Sun, Sep 15, 2019 at 7:39 PM Gabriel Caruso
wrote:
> Hello Nikita,
>
> Em dom, 15 de set de 2019 às 19:29, Nikita Popov
> escreveu:
>
>> Hi,
>>
>> gcov.php.net used to provide valgrind reports and code coverage for
>> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
>
Hello Nikita,
Em dom, 15 de set de 2019 às 19:29, Nikita Popov
escreveu:
> Hi,
>
> gcov.php.net used to provide valgrind reports and code coverage for
> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
> building new versions of PHP there gets very hard. The valgrind rep
Hi,
gcov.php.net used to provide valgrind reports and code coverage for
php-src. It no longer works with 7.4/8.0, because the OS is very old, and
building new versions of PHP there gets very hard. The valgrind reports
have essentially been subsumed by asan/ubsan on Azure Pipelines, but we're
still
