unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 19811@debbugs.gnu.org
Subject: bug#19811: Attempt to graft texlive times out after one hour
Date: Sat, 07 Feb 2015 20:53:33 -0500	[thread overview]
Message-ID: <8761bd2moy.fsf@netris.org> (raw)

On my i686 Libreboot X60, two consecutive attempts to run "guix package
-u" have failed with the following message:

--8<---------------cut here---------------start------------->8---
grafting '/gnu/store/i8iiv9qd1jndwxxr2h563fwwn0997xkx-cups-2.0.1' -> '/gnu/store/nrdr51fkncjm5nqkx70576g25l4ka5na-cups-2.0.1'...
grafting '/gnu/store/y2f71ym41fp803ysf62k1ajk687xd684-xsensors-0.70' -> '/gnu/store/vhjp122fax73k4vags86q6gqzk5qj232-xsensors-0.70'...
building of `/gnu/store/an8an36igcaasvg72kcjph7ns7ssgy6d-texlive-2014.drv' timed out after 3600 seconds of silence
cannot build derivation `/gnu/store/c2fab7ppy5xqgsglvkdp489n95278izx-profile.drv': 1 dependencies couldn't be built
guix package: error: build failed: build of `/gnu/store/c2fab7ppy5xqgsglvkdp489n95278izx-profile.drv' failed
--8<---------------cut here---------------end--------------->8---

I guess that my machine and rotating disk are too slow to graft texlive
within an hour.

Apart from that, there are a few specific problems:

* It never notified me that it was grafting texlive.  Are those messages
  not printed until after the grafts have completed?

* I later discovered the --timeout option for 'guix build' (also
  supported by 'guix package') but the manual claims that "By default
  there is no timeout".  This seems to be incorrect.

     Mark

             reply	other threads:[~2015-02-08  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08  1:53 Mark H Weaver [this message]
2015-02-08  2:42 ` bug#19811: Attempt to graft texlive times out after one hour Mark H Weaver
2015-02-08  2:49   ` Mark H Weaver
2015-02-08  5:09 ` Mark H Weaver
2015-11-16 13:25   ` Ludovic Courtès
2017-10-18 23:50     ` Ricardo Wurmus
2017-10-19  7:26       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761bd2moy.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=19811@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).