all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 35181@debbugs.gnu.org
Subject: bug#35181: Hydra offloads often get stuck while exporting build requisites
Date: Mon, 08 Apr 2019 03:13:39 -0400	[thread overview]
Message-ID: <87a7h16kap.fsf@netris.org> (raw)
In-Reply-To: <87ef6d6mdn.fsf@netris.org> (Mark H. Weaver's message of "Mon, 08 Apr 2019 02:28:41 -0400")

The same jobs that are consistently getting stuck offloading to
hydra.gnunet.org (Hydra's only functional x86 build slave at present)
built successfully on armhf, with build times of 1-2 hours.

With only one x86 build slave and all armhf build slaves on the same
network and running the same ancient version of guix (circa 0.12.0),
there are several possibilities:

(1) The problem might be specific to hydra.gnunet.org or its network, or
(2) it might depend on the version of guix running on the build slave, or
(3) it might depend on the architecture of the build slave, or
(4) something else?

Also, these same jobs built without incident back in early December.

       Mark

  reply	other threads:[~2019-04-08  7:16 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 [this message]
2019-04-08  8:19       ` Ludovic Courtès
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=87a7h16kap.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=35181@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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.