From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Woodcox Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Date: Wed, 31 Oct 2018 20:58:21 -0600 Message-ID: References: <33017962-EFD3-4931-A7FA-22EC3E25B073@inskydata.com> <87y3ae6k0y.fsf@netris.org> <87o9b97f5t.fsf@netris.org> Mime-Version: 1.0 (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]:59152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gI3Cv-0007N0-TQ for help-guix@gnu.org; Wed, 31 Oct 2018 22:59:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gI3Cs-0000cP-Lu for help-guix@gnu.org; Wed, 31 Oct 2018 22:59:41 -0400 Received: from mail.inskydata.com ([184.68.229.6]:6073 helo=server.inskydata.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gI3Cs-0000Tq-Fc for help-guix@gnu.org; Wed, 31 Oct 2018 22:59:38 -0400 In-Reply-To: <87o9b97f5t.fsf@netris.org> 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: Mark H Weaver Cc: help-guix@gnu.org Hi Mark, Thanks for the debugging tips. I will try your suggestions next and see where it takes me. > On Oct 31, 2018, at 7:35 PM, Mark H Weaver wrote: >=20 > Hi Brian, >=20 > Brian Woodcox writes: >=20 >> This is what is displaced on the screen when the hang occurs: >>=20 >> =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 >=20 > 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. >=20 > At this point, I see a few possible next steps, from easy to harder: >=20 > (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. >=20 > (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. >=20 > (3) If you felt like getting your hands dirty and digging deeper to > investigate this problem and find its source, read on: >=20 > 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. >=20 > /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: >=20 > env -i `which bash` >=20 > 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. >=20 > 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". >=20 > 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. >=20 > Hopefully one of these options is workable. Sorry for the bother. >=20 > Regards, > Mark