From: Efraim Flashner <efraim@flashner.co.il>
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: Sun, 7 Apr 2019 20:31:05 +0300 [thread overview]
Message-ID: <20190407173105.GB1337@macbook41> (raw)
In-Reply-To: <87imvp7ogv.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Sun, Apr 07, 2019 at 12:45:57PM -0400, Mark H Weaver wrote:
> I wrote earlier:
>
> > It has become extremely frequent for builds offloaded by hydra.gnu.org
> > to its x86 build slave hydra.gnunet.org to get stuck indefinitely while
> > exporting prerequisites for the build to the build slave.
> >
> > As I write this, both of hydra.gnunet.org's build slots (one for
> > x86_64-linux, and one for i686-linux) are stuck in this way. Here are
> > the stuck builds:
> >
> > https://hydra.gnu.org/build/3432052
> > https://hydra.gnu.org/build/3432472
>
> I'll leave these builds in their stuck state for at least the next 10
> hours or so, in case someone wants to investigate.
>
For these two specifically it's possible that they are just really
really big.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-07 17:32 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 [this message]
2019-04-08 6:28 ` Mark H Weaver
2019-04-08 7:13 ` Mark H Weaver
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=20190407173105.GB1337@macbook41 \
--to=efraim@flashner.co.il \
--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.