Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112317 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47160 invoked from network); 30 Nov 2020 15:40:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Nov 2020 15:40:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 682BA1804A8 for ; Mon, 30 Nov 2020 07:07:32 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 30 Nov 2020 07:07:31 -0800 (PST) Received: by mail-lf1-f48.google.com with SMTP id u19so22268741lfr.7 for ; Mon, 30 Nov 2020 07:07:31 -0800 (PST) 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=lqWx1sJCPdstlCINAy/feBuikZ+U5VHJLDHBKs59mD8=; b=RugucJkSBkX1r+dz+dJILC09J7ZM0wVuLIrOHrX5C9HSBWpSF2C1KejUHaFfxxDFc0 /6ZmbpsjGSJyjY8Lo6VNdDkjSvH5UlXZPw9aOc+6pNvrBYCHyuyFF0yM4g9S64V4VUcn H6hoGs1WxW9F5ELW8pHncKDHastAbJSwK75MJ0Sg+DZIK9gIor7wEhi/yFIBPuNQTq4w hZfsoSD9y2DD2u+i3qf576TJsCwt6Tn3SUxTT3aC++6ZDHrezgIvZhF9MSDA/sQjNd61 LKGxShRn5D6wYSypkFDshLdbl7f0+p7UBZC9o++e6YINTr7O6pHLZESX9hU1w4sfohl0 gV/A== 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=lqWx1sJCPdstlCINAy/feBuikZ+U5VHJLDHBKs59mD8=; b=czFZlbXh6E7VGgF2h9f4vxB8lLzG/Zg7HZeYUYFcuMgVtT7i3/IMsUYc9j3s6LFk6M sxGS24LABk+kd4ogjeJv8hklZbYhEUvceY2Fc9TalGJEW5ZQH6gV+hqGHHgrK8uQFdHi Qo5pNyOVfwcty+N0V4HzOXqUzEqzvs5FlqhT3NaZBVqjsBRcDmsnl2nvnzTvKuptXP9S WdCIzfXp4sDen6BedDScdBZG7K5TsXloBttLqYaUwLwkSyDWSIOuQbGoBXjZgBoR8Thr qAyxQ/6hdhLC0qVL3LYeJb6MufD7BKMT4R6PFmd9TFdLskAy+3qor+Th1ftmAHZWw5R2 VInQ== X-Gm-Message-State: AOAM531PnvWZZ1F0priI8TW7vtBD9T9aB8qHTo4VxF/DO5c+wyLqveeP 8+12AqQFKJGOWe2V8HWgkml5uBkyDAi8mnHhOJM= X-Google-Smtp-Source: ABdhPJymjmzyDZ5fraScFm4+Oeep7/mxPyQQOZAx1W+NoKlh6gSR8UoPq/ROsw0jLzJY/EwFHZkij03ZFv3spztENCA= X-Received: by 2002:ac2:5f56:: with SMTP id 22mr10176135lfz.439.1606748850147; Mon, 30 Nov 2020 07:07:30 -0800 (PST) MIME-Version: 1.0 References: <8caf76f8d4374cde64343132fa8f2ba1d0debe7a5bc4a05f346f67fdabe499f7@mahalux.com> In-Reply-To: <8caf76f8d4374cde64343132fa8f2ba1d0debe7a5bc4a05f346f67fdabe499f7@mahalux.com> Date: Mon, 30 Nov 2020 16:07:13 +0100 Message-ID: To: =?UTF-8?B?TWljaGFlbCBWb8WZw63FoWVrIC0gxIxWVVQgRkVM?= Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000074d51705b5545e8d" Subject: Re: [PHP-DEV] Nightly builds From: nikita.ppv@gmail.com (Nikita Popov) --00000000000074d51705b5545e8d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 28, 2020 at 12:44 PM Michael Vo=C5=99=C3=AD=C5=A1ek - =C4=8CVUT= FEL < vorismi3@fel.cvut.cz> wrote: > Hi internals, > > currently, as far as I know, php does not have nightly builds. > > By nighly I means builds/releases that are tested to pass all CI tests. > This is not the case with master branch, as that branch can be failing > tests. > > I propose to introduce "nightly" branch that will point to "the latest > master head that passed all CI tests". To limit cache misses on > dependent projects/builds (like docker images), I propose to update > "nightly" branch no more than once per day. > > This will allow php comunity reliable testing of new language/engine > features much more sooned until next php minor version has an alpha > release. > > What is your opinion on this and is here someone that can implement it? > > With kind regards / Mit freundlichen Gr=C3=BC=C3=9Fen / S p=C5=99=C3=A1te= lsk=C3=BDm pozdravem, > > Michael Vo=C5=99=C3=AD=C5=A1ek > =C4=8CVUT FEL Hey Michael, It's not entirely clear to me what you're asking for here. Is it about producing actual build artifacts? It's not possible to produce useful build artifacts for PHP, because the number of dynamically linked libraries will make them non-portable. The only thing we could produce are Docker images -- and other people already provide that service. If what you want is to just determine whether a certain commit is a good base for a nightly build, I'd suggest finding our how to query scheduled builds on Azure pipelines (builds like these: https://dev.azure.com/phpazuredevops/PHP/_build/results?buildId=3D13228&vie= w=3Dresults) and check whether they pass. Note though that these will commonly fail even on good commits, because they run tests in more than 60 different configurations, and as such spurious failures are common. Nikita --00000000000074d51705b5545e8d--