From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id IDKvMLai02VAXgAA62LTzQ:P1 (envelope-from ) for ; Mon, 19 Feb 2024 19:49:26 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id IDKvMLai02VAXgAA62LTzQ (envelope-from ) for ; Mon, 19 Feb 2024 19:49:26 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=EIq8qxBQ; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=protonmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708368566; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=GRbHhenUUMxYdtKZI8yYpgGP9hCqgwhDxRqkGgthQok=; b=mi9/94GLsZoGN3tjYQlHoa+SAB38ABXICabvKbUbC864CUoMP2hL/lngFbJJK3lSlafE2W bb7+TcIvBNARpOC5AOTNli4o00CDgklH82nmu1HSM3wFOBn6PVX6Nq+PztUy8DvsJAZos1 OHszTlJyIj2JlEuD/d/a+535Him+ffoeHiNppYGkq/b2Qwv57Xon56j0RLafUC2gKfNsFd 24/nCjGOvWbyOq3gUFxVzVAQ3qA9IEWm6REl4mlQmZQ1blLvZIgq3GOUbuEkLLl5oOReeC 2H0+1wRs2AodXfGzARCbJq0OfpAKMI8auZQK8nmo9/Y02OwgV0qbPIRKpZQkTw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=EIq8qxBQ; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=protonmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708368566; a=rsa-sha256; cv=none; b=kIV4gGWdq8M6uAXrFs1q4w137FnPvqBpQwKVpnxUlvDPr0SETxabTSGmQXX7gdHPk+QeI7 eUyHIqrNVPvoe5iCvEPYQIhpqaIje4kLREpP9TrlfGb1ecvSRprOTBz/bMPBf1wORsx15G uIp/7ZiA0s+cwKcmIVTzkzygMNkIKp3nzgDOpi3Fyi/NOMJ0tSWXtEWE2ekr0OB5ll483F OcVYHDutzaAOo/7fEjeCXebnj0WR/6mOlHdSUXS9RLF8OVmLTHaFcyLONJ6rEZsGGXZmXm VhRUCg/J7SBCRfrboJjxTiFg/EQdeUr9eBRzZK0ET/ZErXiV2sjl6dqBi2TmGQ== 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 9ACA673DDC for ; Mon, 19 Feb 2024 19:49:26 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rc8hH-0006hQ-Dp; Mon, 19 Feb 2024 13:48:59 -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 1rc8hG-0006h8-79 for help-guix@gnu.org; Mon, 19 Feb 2024 13:48:58 -0500 Received: from mail-40134.protonmail.ch ([185.70.40.134]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rc8hD-0002lq-Kk for help-guix@gnu.org; Mon, 19 Feb 2024 13:48:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1708368532; x=1708627732; bh=GRbHhenUUMxYdtKZI8yYpgGP9hCqgwhDxRqkGgthQok=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=EIq8qxBQtRPYKohNr8USgSamfLwCh9A3UHH/gSiqjFC4TtcSf9aea1/8q629RpJs7 shKWGhYMFxRu+g/Sggwea3T6FpvtL62XWrp+vJXkOt/jvc6ItYimLjelNXAIoYuOaF dPRFsfdWOz8wvmmZHjBx93W99cclrtpFqfBPlgNHo3H88OPHayH172OWUseCHzva4j gxMMOIDj9buy9UOc0UYSby057nbomzPscx5FNX/oBoUqeuWynnw3id33Y64fhxUKLf uiUpFhJ4ZJJdAWsZIGBM9AwuLSH0xm6Me9Ps2qEnVdJLJbMI5nJUsXsf5GX9t8bc6q jPfm2tGMf4h4g== Date: Mon, 19 Feb 2024 18:48:30 +0000 To: Carlo Zancanaro From: Skyler Ferris Cc: help-guix@gnu.org Subject: Re: Proper use of `guix build X --rounds=2` Message-ID: <66a474e1-bc23-4e28-979b-34b5f0e30710@protonmail.com> In-Reply-To: <87r0h9gxvd.fsf@zancanaro.id.au> References: <2d797b5b-5bc7-4f68-8287-be148ba6bacd@protonmail.com> <87r0h9gxvd.fsf@zancanaro.id.au> Feedback-ID: 40635331:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.40.134; envelope-from=skyvine@protonmail.com; helo=mail-40134.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -6.42 X-Spam-Score: -6.42 X-Migadu-Queue-Id: 9ACA673DDC X-TUID: hfadP/JwRTPw On 2/18/24 15:23, Carlo Zancanaro wrote: > I'm not sure if this is considered a bug or not, but the solution to > your problem is to use --check. Using your test file running: > > guix build -f test.scm --check > > should run the build one time, and compare the output with what is in > the store. Then: > > guix build -f test.scm --check --rounds=3D2 > > should run the build twice, and check against the output that is already > in the store. Thanks for clarifying! Now that you've pointed out this distinction, it=20 makes sense and shouldn't cause significant problems for me moving forward. > It's a bit confusing, but --rounds only applies if there is actually a > build to do, whereas --check forces a build and compares against the > store. Yeah, the interface does seem a little confusing. There's probably a=20 more intuitive way to present this, but I don't know why the options=20 ended up this way to begin them or what the implications of a change=20 would be. I do see now that the manual notes in the `--check` section=20 that one of the uses is to check that a build is deterministic. I have=20 some understanding of `guix challenge`, but only thought about it for=20 the purpose of checking whether or not the substitute server is=20 providing trustworthy builds not for checking the package itself, so my=20 mind didn't go there when thinking about this problem.