From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#35529: libdrm fails to build on armhf-linux Date: Mon, 06 May 2019 09:15:43 +0200 Message-ID: <874l68qcio.fsf@elephly.net> References: <87d0l1n97o.fsf@netris.org> <87k1f8gl7k.fsf@elephly.net> <87imuosew7.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:36931) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNXrz-0006vv-43 for bug-guix@gnu.org; Mon, 06 May 2019 03:17:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNXry-00076Q-2u for bug-guix@gnu.org; Mon, 06 May 2019 03:17:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42067) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNXrx-00076K-WB for bug-guix@gnu.org; Mon, 06 May 2019 03:17:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNXrx-00031U-N2 for bug-guix@gnu.org; Mon, 06 May 2019 03:17:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87imuosew7.fsf@netris.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 35529@debbugs.gnu.org Hi Mark, > Ricardo Wurmus writes: > >> Mark H Weaver writes: >> >>> Hydra failed two consecutive attempts to build libdrm on armhf-linux: >>> >>> https://hydra.gnu.org/build/3481547#tabs-summary >>> >>> Both build attempts were made on hydra-slave2, which is a Wandboard Quad >>> based on the Freescale i.MX6 SOC. >> >> This has built fine on berlin. We have a completed build for >> /gnu/store/3c28p8b07709isd9jlcnnnyrpgz4ndz8-libdrm-2.4.97. > > What kind of hardware was it built on? I=E2=80=99m not sure. We=E2=80=99re using a few Overdrive 1000 machines th= at have quite a bit more RAM than the other armhf nodes. > Note that the failure on Hydra was due to a timeout in the test suite: > > https://hydra.gnu.org/build/3481547/nixlog/6/tail-reload > > All of the other tests completed within a few seconds, but the timeout > tripped after 1200 seconds. So, I'm not sure if it's simply that the > build hardware is too slow. It might have actually gotten stuck. > Perhaps the test uses /dev/random (as opposed to /dev/urandom) and > there's not enough entropy available on the build machine. My guess is that it ran out of RAM and began trashing. We=E2=80=99ve had at least another build (nss) that worked fine on the Overdrive but failed on other armhf machines. --=20 Ricardo