From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: End of beta soon? drop i686? Date: Tue, 11 Dec 2018 21:22:33 +0100 Message-ID: <20181211212233.21106b5e@scratchpost.org> References: <87y38val12.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/auuZolGjNUp0l923XhnblV3"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59427) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gWoYK-0006dS-De for guix-devel@gnu.org; Tue, 11 Dec 2018 15:22:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gWoYF-00053J-C4 for guix-devel@gnu.org; Tue, 11 Dec 2018 15:22:48 -0500 Received: from dd26836.kasserver.com ([85.13.145.193]:49420) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gWoYE-00051D-4e for guix-devel@gnu.org; Tue, 11 Dec 2018 15:22:42 -0500 In-Reply-To: <87y38val12.fsf@netris.org> 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: Mark H Weaver Cc: guix-devel@gnu.org --Sig_/auuZolGjNUp0l923XhnblV3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Mark, > Note that we also lost 'icecat' on armhf-linux with the 52->60 upgrade, > because our 'rust' packages have never worked on armhf-linux. Wait, what? I wasn't aware. Let's track this as a bug - that's definitely not supposed to happen. mrustc works on armhf - I tested it on physical armhf hardware before mergi= ng. So one of the other Rusts doesn't work? I'll check out Hydra logs... https://hydra.gnu.org/build/3215481/nixlog/1/raw indicates a timeout of silence - we might want to increase it. (this particular step takes many many MANY minutes on x86_64, too). Would that be the "(properties '((timeout . 3600)))))" thing? Or is a "timeout of silence" an extra setting? --Sig_/auuZolGjNUp0l923XhnblV3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlwQHIkACgkQ5xo1VCww uqVQ3gf7BVU6+NB+unEZuJCgzIveL++t+jOjQjCPkndTvddiyJ4UQhBD8wD6NEUW /AzNX12NCDsMdt0eZVoIzwOTY3llF5ecVGwEHpmfoI/latwofE+P2rzfVMh38ih4 9owCkKGKMap45WpB64vyyPBSnE4Svj2XtKbDyugHAPgbzVkD4fa+Wf543ZT6njXp QElGw0wzYUdWMX+5pm+DdAGLSwm8q+tdA6ta9pnV6SpnK9rBiE58dwyxQyv6kr66 Ad9Llcxbw7A3txtT4W4+Ct7XfLvDaW8MgeZC7zaCQcHAAh8Hs2Wi83u0p4Q+LCxn +ueI5f7zXfHNs9EODPKkulfAvIJmDg== =XgZw -----END PGP SIGNATURE----- --Sig_/auuZolGjNUp0l923XhnblV3--