From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id cHGEJsSe7mPTnQAAbAwnHQ (envelope-from ) for ; Thu, 16 Feb 2023 22:23:16 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id CHPSJcSe7mM1oQAAG6o9tA (envelope-from ) for ; Thu, 16 Feb 2023 22:23:16 +0100 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 677E02BB7D for ; Thu, 16 Feb 2023 22:23:16 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=famulari.name header.s=mesmtp header.b=wO2WAAHQ; dkim=fail ("headers rsa verify failed") header.d=messagingengine.com header.s=fm1 header.b="s/Je3JJG"; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1676582596; a=rsa-sha256; cv=none; b=Uhy96cyOnMvE2aQgCBriVCwsl80VFRyuYERa7+ocVuqSKBdoS9tS/hlyp/Ty7Sr9wGLvGM Ndeu318IZuEpbNYeITwt65cpYcU+7vWt8f3y9fsBdbU9eYioBV8trlAaYMXegeZ4vWb5so 2cnhGcjIbAQtcCXtgzLrlQNlFln4Tq8Y4u0pwk6/Q9H0uPtDCCm6IxrZFjpTCKLqTrYr7w MtYJ/A+iX/8T+YITq9tslE7SRFZHJH/bDbA2WDi9VvdXG7pWhY8h/vZHGoDJDHjs2RSolH LjW61aa2MsO6nJAjrE9dqVo1ZN/2uPVze8yidkpeK8zGHJCssAAsJ01yRJF3oQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=famulari.name header.s=mesmtp header.b=wO2WAAHQ; dkim=fail ("headers rsa verify failed") header.d=messagingengine.com header.s=fm1 header.b="s/Je3JJG"; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1676582596; 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:dkim-signature; bh=sDC+YlwNxbcbcmk8ldQdYc6WH/eXz2enetjthXfeOA4=; b=fsQMN1HjhTosUSpbt+tjb557NlCOdKcE93OPWb+pgF5wNO8VBbV95HDuVomoZAWti9dIQ/ Z75gFu6txZUrN45MfkrqEwsbSDJHl0Vp43/8fIq8V3RJb9S1JEw/PSooPBTLyRBEWiL22G G1GKldqP6v9MX6cK3MrxiJosbUnJ8ykjjDabcL81zxe9CB+oKdEVO77C6B5QEuxeOVSOaO KWBEvQfuAoC0f0ZNzJZUiwf4qFDONj9SQuCwAnRCXdU0CM1G5PcJbDlPkqIv4qB0bzWYE/ 9u/lvvqcvhup4HXUgP5AiT90iPY/oS+lKgnqOdniSX+QMMRXCOZjx6KVjYGq9A== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pSli7-0007Wg-Fn; Thu, 16 Feb 2023 16:22:35 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSli5-0007WV-Vx for guix-devel@gnu.org; Thu, 16 Feb 2023 16:22:34 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSli3-0006hs-11 for guix-devel@gnu.org; Thu, 16 Feb 2023 16:22:33 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id AD2A25C00E2; Thu, 16 Feb 2023 16:22:29 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 16 Feb 2023 16:22:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=famulari.name; h=cc:cc:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=mesmtp; t=1676582549; x=1676668949; bh=sDC+YlwNxbcbcmk8ldQdYc6WH/eXz2enetjthXfeOA4=; b=wO2WAAHQ8JCq hk16VjEbqmTsH9B5Uw9Q2ft7nC4E8Tt7u7WDRdiE74/41+CQ5kNRmy9mSmT2eO/M /zYVhoov6NYj20F3v/Nw/uisV61+M5ymVlZqGp03Di63xOAyqlZj4gXv+/EWmL0+ 1QdNcwGV99KAvhuMstPgnItIn+VFwA0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1676582549; x=1676668949; bh=sDC+YlwNxbcbcmk8ldQdYc6WH/eX z2enetjthXfeOA4=; b=s/Je3JJGUbU0TEIFZ+V04zs2VZ4aBbSEHqPyR7zEor0k yeLqIFHE4JQSZw5cHN4wbh5oNjNucpoNoVqn1p/FXHzmjolj0zrvD3rd02K51ghj u+j75HwpoXe9fcBj2kvzHPL+jh6ctSn3iuupcQ+k7XJNenrDsKY33vqx15U9IDdj 43KlF7BHhq1dx62R7kswP/t2igxyX89JOqUlDjdL++qOjJKJWSmM1NukQIBDnrEI aHD/GSKWnI3CKMpWey1PmbJS6t7uHLBXFKTwpR76zk5c/IwF+iqkZecrGVrWa1Qi xZj0/MrLXR1kJFdnieaDJCEvWTHygK4fMMLBEGz+UQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeijedgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefnvgho ucfhrghmuhhlrghrihcuoehlvghosehfrghmuhhlrghrihdrnhgrmhgvqeenucggtffrrg htthgvrhhnpeeiteduheefkeeufeelgeduhfejgfelheefleeuhfeffffgueduleehvdej leeiteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hlvghosehfrghmuhhlrghrihdrnhgrmhgv X-ME-Proxy: Feedback-ID: i819c4023:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 Feb 2023 16:22:28 -0500 (EST) Date: Thu, 16 Feb 2023 16:22:27 -0500 From: Leo Famulari To: Josselin Poiret Cc: John Kehayias , guix-devel@gnu.org Subject: Re: Golang go-updates feature branch? Message-ID: References: <87h6x0ac90.fsf@protonmail.com> <87y1p0aqo0.fsf@jpoiret.xyz> <87k00hs7e1.fsf@jpoiret.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87k00hs7e1.fsf@jpoiret.xyz> Received-SPF: pass client-ip=66.111.4.29; envelope-from=leo@famulari.name; helo=out5-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: X-Migadu-Queue-Id: 677E02BB7D X-Spam-Score: -0.22 X-Migadu-Spam-Score: -0.22 X-Migadu-Scanner: scn0.migadu.com List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-TUID: m7AU6l6ad3y/ On Thu, Feb 16, 2023 at 09:05:42PM +0100, Josselin Poiret wrote: > What's the reason behind branch-specific manifests? I'd imagine we'd > want to test that Guix as a whole still works, even when upgrading just > specific parts. Otherwise, I guess this shouldn't qualify for a blog > post, maybe the cookbook but I'd even just add this as a comment at the > very top of `build-aux/cuirass/evaluate.scm`, since that's where people > will go looking for it. If it does end up becoming widespread, perhaps > a section of the manual/cookbook dedicated to how feature branches work > could be a nice home for these bits of info. Well, now that you ask, I guess there's not a good reason to use manifests here. After creating the kernel-updates CI job based on a manifest, I figured we'd use the same pattern for this, but I agree it's a bit clunky. On the other hand, Cuirass does tend to obscure the salient information when testing a branch that doesn't rebuild the world (i.e. core-updates). For example, for kernel updates, I want to know 1) if the kernel packages built and 2) do the system tests still pass? If I simply asked Cuirass to build everything on the kernel-updates branch, it might end up showing me the result of a bunch of unrelated package builds just because they happened to be selected as part of this jobset rather than 'master', due to (un)lucky timing. Does that make sense? Zooming out, our tooling still has a very long way to go. There are so many crucial features of Nix's Hydra (which we used previously) that we are still missing from Cuirass, and it's made it *much* more difficult to efficiently and carefully perform big updates to Guix, even though the build farm hardware is more capable than when we used to run Hydra. This was all so much easier with Hydra. Sorry for the rambling response that went off-topic. This has been on my mind.