From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#32511: mariadb 10.1.35 fails to build on x86_64 Date: Thu, 23 Aug 2018 16:07:26 -0400 Message-ID: <87a7pcg83l.fsf@netris.org> References: <87a7pdm6t6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51894) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsw38-0005PK-M3 for bug-guix@gnu.org; Thu, 23 Aug 2018 16:17:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fsvve-0006R7-Gu for bug-guix@gnu.org; Thu, 23 Aug 2018 16:10:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:54086) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fsvve-0006R0-Cz for bug-guix@gnu.org; Thu, 23 Aug 2018 16:10:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fsvve-0005pN-3F for bug-guix@gnu.org; Thu, 23 Aug 2018 16:10:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87a7pdm6t6.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 23 Aug 2018 17:38:45 +0200") 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 32511@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > On berlin, mariadb 10.1.35 has one test failure (this is > /gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv, as > found in Guix commit b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, for > instance): FWIW, after staging was merged, I also ran into a problem building mariadb on my x86_64 GuixSD system, where I build everything locally. It failed several times in a row, always with just 1 test failure. The problem turned out to be that I didn't have enough free disk space. Buried in the mountains of output, which I found quite difficult to navigate (searching for "[ fail ]" helped), I eventually found a message about unsufficient space. 5 GB of free space wasn't enough, but ~12 GB was. Mark