all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 35181@debbugs.gnu.org
Subject: bug#35181: Hydra offloads often get stuck while exporting build requisites
Date: Mon, 08 Apr 2019 10:19:18 +0200	[thread overview]
Message-ID: <87pnpw29kp.fsf@gnu.org> (raw)
In-Reply-To: <87ef6d6mdn.fsf@netris.org> (Mark H. Weaver's message of "Mon, 08 Apr 2019 02:28:41 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> The source checkout currently being transferred for build 3432472
> (/gnu/store/…-font-google-material-design-icons-3.0.1-checkout) is 176
> megabytes uncompressed, as measured by "du -s --si", which is not
> precisely same as NAR size, but hopefully close enough for a rough
> estimate.  As I write this, build 3432472 been stuck here for 24 hours
> 15 minutes.  Even if the average transfer rate were 4 kilobytes per
> second, it should have been done in half that time.

This is weird, could it be that data transfers get stuck somehow?  Did
you try to check the status of the ‘nix-store’ and ‘guix offload’
processes on the head node?

I just checked and apparently this package builds fine on berlin.

Thanks for investigating,
Ludo’.

  parent reply	other threads:[~2019-04-08  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 16:41 bug#35181: Hydra offloads often get stuck while exporting build requisites Mark H Weaver
2019-04-07 16:45 ` Mark H Weaver
2019-04-07 17:31   ` Efraim Flashner
2019-04-08  6:28     ` Mark H Weaver
2019-04-08  7:13       ` Mark H Weaver
2019-04-08  8:19       ` Ludovic Courtès [this message]
2019-04-08 19:40         ` Mark H Weaver
2019-04-09 10:54           ` Ludovic Courtès
2019-04-09 18:09             ` Mark H Weaver
2019-04-09  1:06         ` Mark H Weaver
2019-04-09 10:56           ` Ludovic Courtès
2023-04-14 13:15           ` Maxim Cournoyer

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

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

  git send-email \
    --in-reply-to=87pnpw29kp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35181@debbugs.gnu.org \
    --cc=mhw@netris.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.