Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107114
Return-Path: <carusogabriel34@gmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 91716 invoked from network); 15 Sep 2019 20:02:29 -0000
Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12)
  by pb1.pair.com with SMTP; 15 Sep 2019 20:02:29 -0000
Received: from php-smtp3.php.net (localhost [127.0.0.1])
	by php-smtp3.php.net (Postfix) with ESMTP id AB6BC2CF1CB
	for <internals@lists.php.net>; Sun, 15 Sep 2019 10:39:11 -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,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN:  
X-Spam-Virus: No
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a])
	(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 <internals@lists.php.net>; Sun, 15 Sep 2019 10:39:11 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id g207so7554032wmg.5
        for <internals@lists.php.net>; Sun, 15 Sep 2019 10:39:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=EKCpwAtXrG+cPBW+kY/WT6iitZQjSWk+Ut43CDGFxAk=;
        b=OuP8VAL5sSxVoDKsNMfVp/1qNtBRckzPoUNrNlShj9nZei2MttSCRbO1A38Djaovmh
         sNTtN07fq9rPG28L1H+v1IPBbeawZWU8jRss53ibY4ctIyM6eTDTWWDCCqHHQAZLuEEv
         oSLORQrTTir0e/60IutjiyIXTus/TM8mCilWKmxEYfiUdFEJRArgoXqYWUT3hFiRnZJp
         6rM4t6xJC1x2wREKxITWhC2XdJWmuKlO+btEHqtBalM48MIqG2mu51Wsr0YMoe65yYYp
         Af6lXjgGELHlbHqYDkTH3uC5bGM4ckd/mzvz8myxu9iCKssYevLk67VhOOvTtgO+y+MY
         +UgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=EKCpwAtXrG+cPBW+kY/WT6iitZQjSWk+Ut43CDGFxAk=;
        b=Ve7WMO/IUykbmAg+jfhumi2TSXWpPigTkFkKLD0yaOhuDP4P/fXqTuqeRk+PyRMAq/
         aEWCe/4v82T0X/2kgjKTp1h9XiMn71qbQVqUUUH6HYRg84bHyCnMUKM1hq2TJ6CItijl
         E+2WQASSO3vvqUFdOXt3WqMoMG6SF6P2eYawXimRmAohs2QWKvBp7Q1wt0PRdNwrK663
         ZffIqQNAauiVHMMabJR9H79Q18xGXnXQkoOLOvpTL2h5tfYpof4h73Wg8Z8CirPw0hIg
         HvOR9tNmijV0GJEISnYrrxQXeBWDlCI8HQNQjQV2PdHEvp26/R2ytFNYiTg2a6FTBKUt
         e+BA==
X-Gm-Message-State: APjAAAUXCecpdvbCCAzCjGPoz3u4wckFjQGyHNkK1PJhd5fdDWGepeSu
	Aa8zzeeC/ZQdJ/csUTcA57EJAdvGW9QHogW/oSg=
X-Google-Smtp-Source: APXvYqymfruWHTaNkOZ4UPK8kkoYzYAjv9BShfBVYUZBl9COKe88NI7aY2PPU4SRlCVL3M3ePPd5DZo4yRaIHdsVxnI=
X-Received: by 2002:a1c:ca10:: with SMTP id a16mr10975969wmg.1.1568569149875;
 Sun, 15 Sep 2019 10:39:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAF+90c-5LZ4VeyPc3w4dWLFz5tdvYtSctSzSqHFFsmvYwki4gQ@mail.gmail.com>
In-Reply-To: <CAF+90c-5LZ4VeyPc3w4dWLFz5tdvYtSctSzSqHFFsmvYwki4gQ@mail.gmail.com>
Date: Sun, 15 Sep 2019 19:38:58 +0200
Message-ID: <CAP=4hCL2ud7pgj6jagQahOdXsvJmMVqtLS=RT2RQRumL_nfBQA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fbea8105929af607"
X-Envelope-From: <carusogabriel34@gmail.com>
Subject: Re: [PHP-DEV] Computing code coverage on Azure Pipelines
From: carusogabriel34@gmail.com (Gabriel Caruso)

--000000000000fbea8105929af607
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Nikita,

Em dom, 15 de set de 2019 =C3=A0s 19:29, Nikita Popov <nikita.ppv@gmail.com=
>
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 reports
> have essentially been subsumed by asan/ubsan on Azure Pipelines, but we'r=
e
> still missing a replacement for code coverage.
>
> I think it should be possible to set up an Azure Pipelines job that runs
> tests with coverage and publishes it, preferably on Azure Pipelines itsel=
f,
> or if that doesn't work something like codecov.io.
>
> Maybe someone is interested in giving this a try?
>
> Regards,
> Nikita
>

I'm, as I've also reported this a while ago:
https://bugs.php.net/bug.php?id=3D78288.

Do you have something in mind how/what to set up?

Best regards,

-- Gabriel Caruso

--000000000000fbea8105929af607--