From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Disable gnulib's test-lock test in packages? Date: Sun, 29 Oct 2017 16:39:57 +0100 Message-ID: <8760ay2caa.fsf@gnu.org> References: 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]:37398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e8pgx-0005mI-Rs for guix-devel@gnu.org; Sun, 29 Oct 2017 11:40:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e8pgu-0001zR-O6 for guix-devel@gnu.org; Sun, 29 Oct 2017 11:40:03 -0400 Received: from hera.aquilenet.fr ([141.255.128.1]:44466) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e8pgu-0001z9-Go for guix-devel@gnu.org; Sun, 29 Oct 2017 11:40:00 -0400 In-Reply-To: (Eric Bavier's message of "Fri, 27 Oct 2017 21:16:45 +0000") 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: Eric Bavier Cc: "guix-devel@gnu.org" Hi Eric, Eric Bavier skribis: > Several packages (libunistring, gettext, and libidn) in the guix bootstra= p path hang on the "test-lock" test from gnulib while building on a aarch64= system I have access to. Some of them already have a patch applied that i= s supposed to fix the hang on system's with large core-counts, but it seems= ineffective on my system. The findutils package is also affected, and the= re may be others, but I haven't discovered them yet. > > This commit in gnulib fixes the test-lock issue on my system, but doesn't= help until our packages update their gnulib source: > https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=3Dbe95b17ae933323= cb757471f3d7c3f0617f9257e > > Not knowing any better, I created a dummy project to run the latest gnuli= b lock tests, attached for clarity. So are you confident that the above commit fixes the issue? As you might have seen, we already have findutils-gnulib-multi-core.patch, gettext-gnulib-multi-core.patch, and libunistring-gnulib-multi-core.patch, which turned out to be insufficient to fix the problem. > Until the updated lock module and tests make its way into these packages,= I would like to ask if disabling these tests outright would be acceptable,= similar to the attached patch. Thoughts? Your patch looks like the safest approach; you can also remove *gnulib-multi-core.patch while you=E2=80=99re at it. Then I think it=E2=80= =99s OK for =E2=80=98core-updates=E2=80=99. Thank you! Ludo=E2=80=99.