From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Soo Subject: Re: Rust = bust? Date: Sun, 30 Jun 2019 12:59:09 -0700 Message-ID: References: <87woh27ttc.fsf@nckx> <8de3c10f-d698-fcc6-deaf-ed3608ecf73d@riseup.net> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56154) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hhfyj-0000Vm-JP for guix-devel@gnu.org; Sun, 30 Jun 2019 15:59:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hhfyi-0004Ya-GL for guix-devel@gnu.org; Sun, 30 Jun 2019 15:59:13 -0400 Received: from mail-pf1-x442.google.com ([2607:f8b0:4864:20::442]:36821) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hhfyi-0004XJ-1R for guix-devel@gnu.org; Sun, 30 Jun 2019 15:59:12 -0400 Received: by mail-pf1-x442.google.com with SMTP id r7so5463739pfl.3 for ; Sun, 30 Jun 2019 12:59:11 -0700 (PDT) In-Reply-To: <8de3c10f-d698-fcc6-deaf-ed3608ecf73d@riseup.net> 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+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: swedebugia Cc: guix-devel@gnu.org Fortunately, I think rust tests are the longest build phase for rust. So I t= hink even a rebuild of all dependents won=E2=80=99t take more than a few hou= rs without tests. Hope rust is taken care of soon! - John > On Jun 30, 2019, at 12:35 PM, swedebugia wrote: >=20 >> On 2019-06-30 21:32, Tobias Geerinckx-Rice wrote: >> Swedebugia, >> swedebugia wrote: >>> http://ci.guix.gnu.org/search?query=3Drust-1.30 >>> -> >>> http://ci.guix.gnu.org/build/1303680/details "dependency failed" >>>=20 >>> What does that mean? >>>=20 >>> What is going on? >> That a package (well, derivation) upon which rust@1.30.1 depends failed t= o build. >> I'm almost certain that Cuirass doesn't currently track dependency inform= ation the way it eventually should, which would mean there's no way to find o= ut *which* dependency failed. The only way to find out would be build rust@= 1.30.1 yourself and see what fails before you get to it. If you do get to i= t, you managed to build something that ci.guix didn't and you should feel pr= oud. >> I logged into my substitute server to find out more, but: >> athena.tobias.gr ~ =CE=BB guix describe >> Generation 109 Jun 30 2019 21:11:58 (current) >> guix a3d1a34 >> repository URL: https://git.savannah.gnu.org/git/guix.git >> branch: master >> commit: a3d1a3487a34820d2a0b3d5e6206e4df1c77c15c >> athena.tobias.gr ~ =CE=BB guix build rust@1.30.1 >> [=E2=80=A6] >> /gnu/store/p20fkgdlqqw4dlfqg8jximqg6qpcz7a1-rust-1.30.1 >> Looks like I already built the entire rust chain successfully. (?) >> You're welcome to give my substitute server at https://guix. a try (more info at that URL). I'd be interested in both success and fa= ilure. :-) >=20 > Nice, what a gift! >=20 >>> Also could somebody tell me how to shut off the tests if I choose to >>> build them myself? >> Edit the package definition to add =E2=80=98#:tests? #f=E2=80=99 to the a= rguments field. This will change the derivation and all that depend on it (= so you won't get substitutes for anything that depends on your untested rust= fork). >=20 > Yeah, thats the downside. >=20 > --=20 > Cheers Swedebugia >=20