From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Date: Wed, 31 Oct 2018 21:35:31 -0400 Message-ID: <87o9b97f5t.fsf@netris.org> References: <33017962-EFD3-4931-A7FA-22EC3E25B073@inskydata.com> <87y3ae6k0y.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 ([2001:4830:134:3::10]:43807) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gI1uZ-00038o-Sz for help-guix@gnu.org; Wed, 31 Oct 2018 21:36:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gI1uU-0006d0-7h for help-guix@gnu.org; Wed, 31 Oct 2018 21:36:38 -0400 Received: from world.peace.net ([64.112.178.59]:38942) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gI1uP-0006ao-O7 for help-guix@gnu.org; Wed, 31 Oct 2018 21:36:32 -0400 In-Reply-To: (Brian Woodcox's message of "Wed, 31 Oct 2018 14:50:34 -0600") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Brian Woodcox Cc: help-guix@gnu.org Hi Brian, Brian Woodcox writes: > This is what is displaced on the screen when the hang occurs: > > =E2=80=A6 > make check-TESTS > make[3]: Entering directory =E2=80=98/tmp/guix-build-guile-2.2.3.drv-0/gu= ile-2.2.3=E2=80=99 > Testing /tmp/guix-build-guile-2.2.3.drv-0/guile-2.2.3/meta/guile =E2=80=A6 > with GUILE_LOAD_PATH=3D/tmp/guix-guild-guile-2.2.3.drv-0/guile-2.2.3/test= -suite Thanks. These last messages were printed by the 'check-guile' script, just before it passes control to test-suite/guile-test, which runs the tests in test-suite/tests/*.test. I guess it's getting stuck during the initialization of 'guile-test', because it prints a message before running each test. At this point, I see a few possible next steps, from easy to harder: (1) You could wait until hydra.gnu.org comes back online, which I expect to happen sometime next week. Hydra has a full set of substitutes for 0.15.0, so you shouldn't need to build Guile at that point. (2) You could try QEMU instead. I suspect that Guix has seen far more testing under QEMU than VirtualBox, because QEMU is in Guix and not VirtualBox. If it fails in QEMU, then we will have a test case that Guix developers can try to reproduce on their own systems. (3) If you felt like getting your hands dirty and digging deeper to investigate this problem and find its source, read on: You could try the same build with "--keep-failed" added to the Guix command line, and interrupt it after it gets stuck. At that point, you should have write access to /tmp/guix-guild-guile-2.2.3.drv-0, and you can enter that directory and try various experiments. /tmp/guix-guild-guile-2.2.3.drv-0/environment-variables will contain the environment variable settings that were passed to the top-level build commands, including "make check". In that directory, run: env -i `which bash` or a similar command to clear the environment, and then "source environment-variables" to load the environment settings. Then 'cd' into the guile source directory and run ./check-guile. Hopefully it will get stuck here as well. If so, you could use GDB to attach to the stuck guile process and obtain a backtrace. It might also be useful to see the output of "strace -f ./check-guile". There are many other things that could be tried at this point, such as removing the "--debug" flag passed to guile at the end of 'check-guile', inserting debugging print statements at various points in the 'guile-test' script, etc. Hopefully one of these options is workable. Sorry for the bother. Regards, Mark