From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id mDDMAe6ekWAdIAAAgWs5BA (envelope-from ) for ; Tue, 04 May 2021 21:22:22 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id KFXvOO2ekWCnBgAAbx9fmQ (envelope-from ) for ; Tue, 04 May 2021 19:22:21 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id A51131E54A for ; Tue, 4 May 2021 21:22:21 +0200 (CEST) Received: from localhost ([::1]:59382 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1le0ce-0001t9-DY for larch@yhetil.org; Tue, 04 May 2021 15:22:20 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48224) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1le0cU-0001sG-Oz for guix-devel@gnu.org; Tue, 04 May 2021 15:22:10 -0400 Received: from mira.cbaines.net ([2a01:7e00:e000:2f8:fd4d:b5c7:13fb:3d27]:56633) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1le0cS-0002ho-Aw; Tue, 04 May 2021 15:22:10 -0400 Received: from localhost (unknown [IPv6:2a02:8010:68c1:0:8ac0:b4c7:f5c8:7caa]) by mira.cbaines.net (Postfix) with ESMTPSA id 910C327BC81; Tue, 4 May 2021 20:22:05 +0100 (BST) Received: from capella (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id 0e12aa58; Tue, 4 May 2021 19:22:04 +0000 (UTC) References: <878s4ye116.fsf@cbaines.net> <87eeeo24a9.fsf@gnu.org> <87r1iocdok.fsf@cbaines.net> <87r1imsy33.fsf@gnu.org> User-agent: mu4e 1.4.15; emacs 27.1 From: Christopher Baines To: Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: Bringing substitutes from the Guix Build Coordinator to users In-reply-to: <87r1imsy33.fsf@gnu.org> Date: Tue, 04 May 2021 20:22:02 +0100 Message-ID: <87fsz2cnj9.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Received-SPF: pass client-ip=2a01:7e00:e000:2f8:fd4d:b5c7:13fb:3d27; envelope-from=mail@cbaines.net; helo=mira.cbaines.net X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1620156141; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=EcdXjIvGpCIPfaJzyybfLifOubx5lZ66ZpYzss4g3wU=; b=NSnUATwv5XPZ6EBg+tVFiDA55HCqtmHztxMMYLj5QaHoUX9VRtMJCr3IHq/3TYUcNWlA+u oXlH9wkFKwhLYI8I1y0V2eQyVY9fHEB0xNa35A+xTYXNYeemPigAmvoxJCr4pb7SS/h3N8 n7IKFSZHsGHshcMEBpR/YhRsPpBFnUSGLpFwJuX4rSDGpxrNB3no7dbNAiixjms0lxgLnY i4ipWg2kYwS7SWmLIEbSDyT4NSgIjURL654cfEQz/OAa11mZS1h2FzQMVCSOp5+QGAbunL yrFIMTf3rfYsepDM728NQVaeHmQc36KConyWbjVaJKG3hyUTou74dJip0IzA5A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1620156141; a=rsa-sha256; cv=none; b=SIbQG4+9uxzqSjlSKl6DMEDkw9HZNn+Kidb6maTIu3SDrxAJcuagQleLng/3hbYcgrQ523 UrTGa809q1lq+VQZ0Vw2bh/a+2aGo2ZZHzkW/2F+3ilgbXr3lHqvFDfKo6LA9RtyCwNsTM Dtc2e7BfkXENS+GoFYzxMJxqINUDgqcKg//KFCWsvUDhemBErkk/Bp2R9fVl/I5O+IwK3c QfYm/lFllAScR8TTwDUw7u2Co7sE8XdtX+nAlToJVlsrZSHcCDQrFPGJGMs4P2td05O4bz jnXYxbXwJiVDcmXtMIRe2WrRgOHNidPGVNtkEdOTg66mqpeKLiK2gtnKTJj6Ng== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Spam-Score: -3.06 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: A51131E54A X-Spam-Score: -3.06 X-Migadu-Scanner: scn0.migadu.com X-TUID: bk466ysPxURa --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Christopher Baines skribis: > >> Ludovic Court=C3=A8s writes: > >> As people are going to Cuirass to look at the build status for packages, >> system tests and various branches, the problem is similar to that of >> substitutes. It doesn't matter if the Guix Build Coordinator seems to do >> some things better, when the question comes up about whether something >> has built yet, or whether a branch is ready to merge, Cuirass on >> ci.guix.gnu.org is where people are going, and that seems unlikely to >> change (at least less likely than the setup for providing substitutes). >> >> The Guix Data Service in the center, making it easier to do various >> things by providing the data, this was the idea when it started, but the >> reality recently is that strategy hasn't been paying off. > > The Data Service provides a wealth of information that=E2=80=99s underuse= d! > > I think addressing the interface issue (be it web UI or JSON + CLI) is > high priority so we can all start taking advantage of the Data Service. > The current interface is generic enough that it allows you to see > everything, from lint warnings to version changes to reproducitility > rates. > > We could have interfaces that answer very specific needs: > > =E2=80=A2 Which packages are broken on x86_64? While the Guix Data Service can sort of do this (if it has builds data), I think Cuirass has a page for that now, there's not a single URL for the latest evaulation, but assuming you click on the latest one, this page list the failed builds for x86_64: https://ci.guix.gnu.org/eval/30959/dashboard > =E2=80=A2 How does branch X compare to branch Y in terms of build failu= res? > > =E2=80=A2 Which packages are not reproducible? > > =E2=80=A2 Which packages are =E2=80=9Cflaky=E2=80=9D? > > I know all this information is already available from the web UI, but > because it=E2=80=99s generic, it can be hard to find out how to answer ve= ry > concrete issues like this. > > A QA entry point like you proposed in the thread you mentioned=C2=B9 could > certainly help. A reproducibility entry point would be nice too. A > package browser for guix.gnu.org like the one Danjela worked on would be > great too, possibly with version browsing facilities. And Guix Weekly > News! And the security tracker! :-) > > =C2=B9 https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00096.html > > It seems to me that all that hard work is already done and what I > describe above are rather low-hanging fruits. > > Taking Conway=E2=80=99s law into account, we may find it easier to recrui= t if as > much as possible takes place here, things get deployed behind > *.guix.gnu.org, and relevant bits are made part of Guix proper. And > also, we must regularly advertise progress; one blog post in all of the > Guix Data Service=E2=80=99s lifetime is not enough. :-) > > Thoughts? This doesn't really relate to the subject of substitutes. Some of the things you mention do relate to work I'm trying to progress though. I'm still working on automated patch (plus branch) testing, and I think having a simple overview of patch+branch states is hopefully something that I'll get to at some point. On the subject of the patch testing stuff, that isn't under .guix.gnu.org and I haven't written a blog post yet. I can't see Cuirass starting to test patches, but then I wouldn't have predicted it would be managing builds across multiple machines. Maybe there are some risks with the patch testing work that I haven't done enough/the right stuff to mitigate. I've also got too many things in progress at the moment, with the combination of work on substitutes (I hope to implement things set out in [1] some point soon), Outreachy, and the security related work that I'm trying to start, I need to "finish" some things before starting new ones or going back to unfinished things. 1: https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00104.html --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmCRntpfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh aW5lcy5uZXQACgkQXiijOwuE9XdxTg/+N3cZghOCR9HozllS5dnfZSQkf13xHB3b lS5EXlDLwQbdVtQpATGaV9bPK2TkJuSc4mlt4GjqOSvzX25KpLMiOedPJibfyKdZ xwv/gyqhgY2M1Du55Q4Z+4CDjTyv+OAJRrLFKGcqhwx+/LP9us8wh8oWODNeRdKA h1XwU9DYZ07CfMHGwajryzvtCsHnlvq7zFjiFKeiOcr2M+dh70/OlnA8ruv8CRQO uycgccsAqEzPsuEIokk0lExA9ji9RKZnWjdjid473H6RjYxmztlt5nePDRZidItG 0+leL5GkxCuWpJOTNyX9sDWZcy3wLtDGt1Z7bljYgn0xmGIIoT2jJWxD/XxhOGoD yj2xPNw734CUXJqF/GIEsnrhOEEhuxiMPRKK8RwAhJvBTIDmwRylZ6oZ92VmnON2 FgoQKb2t7phP87CTP57JerTUNCyZhKHnLaKrcsPPX5GAHuzTRtz2Cpmke+4H92+v /LJdIrBm7cn4Da0l52+czccRJFK1ke/67YuawDh/1PADxErMz+kClPOu++DHaGbV LTJnLGv3TFMnR6FQvO96UBQvCDqSw0jyQESFjyA8ppWLcG0iWpi+aYLnJ6SBXbFv gAtqODaZqpxANI7AkFiKuz7w54fagis+PZ3vgxhqXJBofrw/FYpkjllKjh7sHBr2 LohIOFIVkjQ= =TMDk -----END PGP SIGNATURE----- --=-=-=--