From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id eA10C1c3uGXkPAEAe85BDQ:P1 (envelope-from ) for ; Tue, 30 Jan 2024 00:40:07 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id eA10C1c3uGXkPAEAe85BDQ (envelope-from ) for ; Tue, 30 Jan 2024 00:40:07 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=k0UCz72Y; 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=pass (policy=quarantine) header.from=protonmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1706571607; 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=X+kittsdavcdwGyyDSfeMuUCu8aBv/musFKen7pzgGo=; b=MX+DbTHqZG8sK9Ay8ALzcJcsTCy9E1TsaYM38RfxrIumwOvECTZlUCUigDkAUwGKy6AhKb OZ5Cb07SigyZVvWQRfa/SKPxg3GZTAxbV5ZTHvOqP3nXex9hx8d2a/PNmg4SW9bqVx5zwh rb8iADj/vhOEX2t5xHH8yfkx5kO4nobpakaq36avj56chLkyLdJttZl25U3kZH1o6Br+m1 EfaZvLTJytaR/Bp9GUj87jVK+D59KprJZoYptwQ5+IHl764N6ZrAIYu4r0cd5WGktYxLnM ha0kK8VAv2R+jMn3Me8mqq2aZc1jXaC0Ej3uREFzveO2+SAe5osQWpSesCR/tA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=k0UCz72Y; 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=pass (policy=quarantine) header.from=protonmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1706571607; a=rsa-sha256; cv=none; b=F+KoiUdW4Kgg14IkqbF4buSTiAPjy0PllV3s6VKFLDRsQUvpKz88S8EBzHkzDROd92PH9S eBh4Qy/afPzJU16C8Ip/J49tuArsCrYTwBaSD3Us82GrZU405ZiU1so+Jk7eJXgP8GqEr5 u0EL0xu/3n6Fa2EZ4fumYJKWZZGHuhWJkxm+KL+90ntqQO7MwEGDRFbJZbMD5QvFRl3hFT bKQE2CNKiTKqu5+zUeVOzdiWEM8bvXvnBqOL44T6NPwuW8fk/0sqnEeoEcCPiE9JpQXo9M katUzeAWprIs/agvsPRaeMVhAFoiTNPP51O4OqhZYhT4tA6vQIgxC3B1waEd9g== 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 12A5943A25 for ; Tue, 30 Jan 2024 00:40:07 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rUbE1-0007i6-23; Mon, 29 Jan 2024 18:39:37 -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 1rUbDi-0007Yv-6q for guix-devel@gnu.org; Mon, 29 Jan 2024 18:39:22 -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 1rUbDf-00062S-St for guix-devel@gnu.org; Mon, 29 Jan 2024 18:39:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1706571552; x=1706830752; bh=X+kittsdavcdwGyyDSfeMuUCu8aBv/musFKen7pzgGo=; 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=k0UCz72YBM60jbC1SkhF06qBVUU9iN7zzCGxiFzVp8hmuFepQOB8i5B7LMwcO1GA6 Vqd9W3L6eGZWduvcl0PbzYYQzW5X2pH0luwC5oeggBwVaVeEdcDNVlj5M4uvRNjWLg y5CgvCprqREUtTJ8hV9EOou2fKH62Ol33pivmxa64cAqRqDjM6551l1f4WaVOHkNqT bfHIOL+iLGVo7m8AEtfbadUE4gi75NKPjRQA/YFUZvzkItb2pX6hht+VLq/oMa9oq1 fkuVj4PECNOwy+dMz6BNThr6TKPYxpkButKnLDuhwPl4PUKHQoVW155ExGVwOZ9qY2 /KtLoX9O9U3dA== Date: Mon, 29 Jan 2024 23:39:01 +0000 To: John Kehayias From: Kaelyn Cc: guix-devel , Efraim Flashner Subject: Re: Update to source-highlight seems to have broken rust Message-ID: In-Reply-To: References: Feedback-ID: 34709329: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=kaelyn.alexi@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_H5=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: 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: 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-Migadu-Spam-Score: -10.08 X-Migadu-Queue-Id: 12A5943A25 X-Spam-Score: -10.08 X-Migadu-Scanner: mx11.migadu.com X-TUID: RNzk8so9nLF4 On Monday, January 29th, 2024 at 9:49 AM, John Kehayias wrote: >=20 >=20 > Hi Kaeylyn, >=20 >=20 > On Monday, January 29th, 2024 at 12:26 PM, Kaelyn kaelyn.alexi@protonmail= .com wrote: >=20 > > Hi Efraim and guix-devel, > >=20 > > Based on my local cuirass instance and some spot testing this morning, = it appears the change to source-highlight in commit 367bc2d198 has broken t= he build of rust 1.73. > > * `guix refresh -l source-highlight` reports modifying the package woul= d require a large number of rebuilds ("Building the following 6129 packages= would ensure 9069 dependent packages are rebuilt"). > > * I am seeing a consistent test failure for rust starting with that com= mit. > > * `guix weather rust@1.73` reports 100% availability for both ci.guix.g= nu.org and bordeaux.guix.gnu.org at commit fbeae77ae6 but 0% availability a= t commit 367bc2d198. >=20 >=20 > This was reverted in 0fb160a5e8b0b800426489c0a2ad387c6934fba so maybe you= were just unlucky in what commit you were at? >=20 > I can't comment on the details of the change or rust, but hopefully just = pulling to a newer commit will go back to good coverage for you as well. >=20 > Hope that helps! That does help, thank you! I think I missed the revert because of a minor m= isbehavior? of cuirass (so me getting unlucky about the commit in a differe= nt way!). I have a local cuirass server set up to build the packages in a local chann= el, along with a job configured to build the packages in my Guix Home confi= gs (currently using a manually generated manifest file that is checked in a= s part of the local channel)--but I don't have notifications set up and I o= nly occasionally check on its status. This morning I happened to notice tha= t wine64-staging was reported as having been failing for a while, because o= f ffmpeg-6.1.1 failing to build due to the rust failure (i.e. cuirass repor= ted ffmpeg as the root failed build, and looking at the error log was what = revealed that it was actually rust that failed). I then mistakenly assumed = the issue was still present because the list of evaluations and evaluation = dashboard reported wine64-staging as still failing up through the evaluatio= n for commit 2c5293a from a few hours prior to my email. I'm guessing the u= nderlying issue for the rebuild not happening for the revert commit is tied= to dependency propagation triggering rebuilds (as a likely-related example= , I find it odd that while cuirass showed the wine64-staging rebuild failed= because its dependency ffmpeg failed to build, but claimed ffmpeg was the = failed package when it was a unit test in the rust build that actually fail= ed). Thank you again, John, for your response about the commit having already be= en reverted! Cheers, Kaelyn > John >=20 > > The consistently-reported failure is: > >=20 > > ---- metadata::cargo_metadata_non_utf8 stdout ---- > > thread 'metadata::cargo_metadata_non_utf8' panicked at crates/cargo-tes= t-support/src/paths.rs:155:33: > > failed to mkdir_p /tmp/guix-build-rust-1.73.0.drv-0/rustc-1.73.0-src/bu= ild/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/tmp/cit/= t1684/foo/=EF=BF=BD/./src: Invalid or incomplete multibyte or wide characte= r (os error 84) > > note: run with `RUST_BACKTRACE=3D1` environment variable to display a b= acktrace > >=20 > > failures: > > metadata::cargo_metadata_non_utf8 > >=20 > > test result: FAILED. 2801 passed; 1 failed; 198 ignored; 0 measured; 0 = filtered out; finished in 92.81s > >=20 > > error: test failed, to rerun pass `--test testsuite` > >=20 > > I don't exactly understand how wrapping scripts in source-highlight end= ed up breaking the above rust test, nor do I use rust, so I wanted to bring= it to folks' attention since the failure appears to affect a great many pa= ckages (I noticed it in an ffmpeg build failure on my local cuirass instanc= e). > >=20 > > Cheers, > > Kaelyn