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 22:33:10 -0400 Message-ID: <87k1lx7chq.fsf@netris.org> References: <33017962-EFD3-4931-A7FA-22EC3E25B073@inskydata.com> <87y3ae6k0y.fsf@netris.org> <8246EDA7-82A1-411C-B1D0-967F9ECF9CF6@InSkyData.com> 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]:51701) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gI2o4-0005KX-Fx for help-guix@gnu.org; Wed, 31 Oct 2018 22:34:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gI2o1-0001JL-Be for help-guix@gnu.org; Wed, 31 Oct 2018 22:34:00 -0400 Received: from world.peace.net ([64.112.178.59]:39054) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gI2o1-0001Ip-72 for help-guix@gnu.org; Wed, 31 Oct 2018 22:33:57 -0400 In-Reply-To: (George Clemmer's message of "Wed, 31 Oct 2018 19:44:09 -0400") 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: George Clemmer Cc: help-guix@gnu.org George Clemmer writes: > Brian Woodcox writes: > >> I think I=E2=80=99ve had it sitting like that for hours. >> >> The reason I think it=E2=80=99s hung in VirtualBox is the fact that with= in >> about 45 seconds there is no longer any activity on the hard disk >> icon. >> >> I am currently installing in Qemu and will see how that goes. > > Dunno about VirtualBox. But I just did 'guix pull' on a fresh 'guix > system vm-image' running on GuixSD in QEMU. It looks the same: 4 CPUs > howling and the hard drive doing hardly anything. But I see this in > /tmp > > g1@sysi53 ~$ ls /tmp > guix-build-guile-2.2.3.drv-0/ > > ... and BOOTSTRP GUILEC steps are trickling out. So even thought it > feels like it, it's not hung. That's during the 'build' phase. The problem Brian is seeing is during the 'check' phase, at a place where there is not normally any significant delay. I already told you this in my last message, but I guess it wasn't clear. Mark