Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107352 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 80798 invoked from network); 30 Sep 2019 14:49:58 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 30 Sep 2019 14:49:58 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 9C2622C2BB4 for ; Mon, 30 Sep 2019 05:30:21 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Mon, 30 Sep 2019 05:30:21 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id v2so37650331iob.10 for ; Mon, 30 Sep 2019 05:30:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=2O/GiWS0j90BbOPJg0Em+5OotLExRMp/Ou2rYRfqgBc=; b=ZmaEMud5Gid3qSm+ppy9qKaRO3ImxbqtdJAB3q6jpryn83dkPilNoPeV7LaVuiumuN KpPJfo7zLAHw3WA7m+7XEZINQ73xhkAxu5X/xLo/6c1BHoAElbbuMaIB+Kg0aZUxL6Gl 4spmE3aubk2Cj9xKLGwAIcS8K2IGIbiaO4Iw2mxMz2ulPai7T4LE42FWS0KIEB3wld5K 5J53dMSfUhESoT/pbAEoui78yDa8bGB4tQa0QTkJuxeOJ9l9EvcJWxkDoSAZ9nnT/QWU cwPvmdRVPrxuE4z2ZozXdAkDT4MU6u6UOzJc2F1fEUW0n/pYGuHdoaeUU8sazOE6cJMP u9VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=2O/GiWS0j90BbOPJg0Em+5OotLExRMp/Ou2rYRfqgBc=; b=XxGD3X14Ithz4lywO0NgD95GuX+eqHqt7DTotQNEYzDX9ni7WEjRPWNnz41/gtgjBH NnjwwwU4iR6OcVaJeRKwxrKXuffJFrMZtcFfNZAhjKlZcZB3VjcLyPAAGtxulm+msfJt yXkE6zqtRUESbEFRB676Rw/6DYw0ouBfI994W4EmUPA7gHyzVdUra1aeXsqXGGIL8E2W MXo1K32w9U9TO1mw49t4+kZWCZOiXYuRCdRvjLu2Etzj6PyqkL1nptM5nHQsdHJGgate yJ1zuwI4SQTYGNt8GnWEokMUekZKWWQSuNe3Pm/apCP6DJ3HTPmBA0wKnIFkQmb1kmVw rMAw== X-Gm-Message-State: APjAAAXoSex5N/cnGjd11MPiOsMzbkr34bt9h5fo+SFiWE6KaQmDb+K8 wErkApozrfdcA77JRkHKG1h9tuT2PaGxkrWPk4Pq2Iz3iCk= X-Google-Smtp-Source: APXvYqzbltlnW8G6iWxl9xY6MCpuvVOPWkczfpZ+y+wCsU/WfhaAk3ytfyRwiHuk6prjIWUIXifjRLxZ8N8JzPeCOkQ= X-Received: by 2002:a02:5dca:: with SMTP id w193mr5235111jaa.94.1569846620577; Mon, 30 Sep 2019 05:30:20 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 30 Sep 2019 13:32:07 +0100 Message-ID: To: nikita.ppv@gmail.com Cc: internals@lists.php.net Content-Type: text/plain; charset="UTF-8" X-Envelope-From: Subject: Re: [PHP-DEV] Computing code coverage on Azure Pipelines From: gerard.roche.php@gmail.com (Gerard Roche) > 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 missing a replacement for code coverage. The index page for v7.4 and the master branch say the build failed but it looks like the valgrind and coverage reports are still generated: http://gcov.php.net/PHP_HEAD/lcov_html/ > The first step is probably to get code coverage working locally. We have a > ./configure --enable-gcov option and there's some extra make targets in > build/Makefile.gcov. Maybe taking a look at what > https://github.com/php/web-gcov/blob/master/cron/cron.sh does would help. > > Second step is to add a new job in azure by copying > https://github.com/php/php-src/blob/master/azure/job.yml and adding the > necessary gcov/lcov magic there. > > The hard part if how to get those results published on Azure under the > "Code coverage" tab. There is a PublishCodeCoverageResults task for this > purpose, but I don't know how one would use that with lcov in particular. > It seems to me that part of it requires a coverage overview in a specific > format and part is just a directory with HTML, so maybe the result from ltp > genhtml can just be used there? Figuring out how to make this work is > likely going to be "fun" ;) > > Nikita Is the intention to close down gcov.php.net completely? re: https://github.com/php/php-src/pull/4746 -- Gerard