From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:47743) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hf20R-0005F4-9w for guix-patches@gnu.org; Sun, 23 Jun 2019 08:54:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hf20Q-0004HP-C4 for guix-patches@gnu.org; Sun, 23 Jun 2019 08:54:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:39479) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hf20P-0004GE-Rv for guix-patches@gnu.org; Sun, 23 Jun 2019 08:54:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hf20P-00039s-O7 for guix-patches@gnu.org; Sun, 23 Jun 2019 08:54:01 -0400 Subject: [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0. Resent-Message-ID: References: <20190617084436.12311-1-glv@posteo.net> <49b66acb-c2f9-5fd0-97aa-16711ae933e1@riseup.net> <87imsx2rk3.fsf@yamatai> From: Guillaume LE VAILLANT In-reply-to: Date: Sun, 23 Jun 2019 14:53:18 +0200 Message-ID: <87blyobgzl.fsf@yamatai> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: swedebugia Cc: 36258@debbugs.gnu.org swedebugia a =C3=A9crit : > It finished compiling on 1 core but the tests stopped after an hour and w= as > completely silent and no cpu use. > > How do I run the tests manually? > > I tried: > cd into /tmp/guix-build-xxx > source the env > cd build > make "ARGS=3D-R 'hash|core_tests'" "test" > but got this error: > Could not find executable > /tmp/guix-build-monero-0.14.1.0.drv-0/build/tests/hash-target-tests That's strange, if the compilation phase finished, the 'build/tests/hash-target-tests' file should exist. Do the 'build/tests/core_tests/core_tests' and 'build/tests/unit_tests/unit_tests' programs exist, or is your 'build/tests' directory empty? Also, 'core_tests' takes a long time to complete (around 40 minutes on my machine I think), and it doesn't print any message while it's running (but there should be 1 CPU core in use).