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 02:28:41 -0400	[thread overview]
Message-ID: <87ef6d6mdn.fsf@netris.org> (raw)
In-Reply-To: <20190407173105.GB1337@macbook41> (Efraim Flashner's message of "Sun, 7 Apr 2019 20:31:05 +0300")

Hi Efraim,

Efraim Flashner <efraim@flashner.co.il> writes:
> For these two specifically it's possible that they are just really
> really big.

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.

I should also note that this is the *10th* attempt for build 3432472.
I didn't realize until now, but I've manually aborted this same build
9 times before now, before filing this bug report.

On its fourth attempt, it ran for just over *48* hours before I aborted
it.  Here's a full list of how long each of the build attempts have run:

  Nr      Duration          Machine Status
  --------------------------------------------------
  1       20h 23m 27s       Aborted (log, raw, tail)
  2       5m 28s            Aborted (log, raw, tail)
  3       1d 9h 54m 42s     Aborted (log, raw, tail)
  4       2d 0h 1m 17s      Aborted (log, raw, tail)
  5       8h 12m 4s         Aborted (log, raw, tail)
  6       1d 21h 37m 24s    Aborted (log, raw, tail)
  7       8h 26m 1s         Aborted (log, raw, tail)
  8       11h 21m 6s        Aborted (log, raw, tail)
  9       4h 38m 10s        Aborted (log, raw, tail)
  10      1d 0h 22m 19s     Building (log, raw, tail)
  --------------------------------------------------
  Source: <https://hydra.gnu.org/build/3432472#tabs-buildsteps>

The other build (3432052) has a very similar story.  Its source checkout
is slightly larger at 287 megabytes, and it's currently on its 8th
attempt, which has been running for 23 hours 27 minutes as I write this.

  <https://hydra.gnu.org/build/3432052#tabs-buildsteps>

  Nr      Duration          Machine Status
  --------------------------------------------------
  1       1d 4h 32m 24s     Aborted (log, raw, tail)
  2       2d 0h 1m 17s      Aborted (log, raw, tail)
  3       8h 12m 5s         Aborted (log, raw, tail)
  4       1d 10h 11m 48s    Aborted (log, raw, tail)
  5       8h 26m 11s        Aborted (log, raw, tail)
  6       10h 49m 44s       Aborted (log, raw, tail)
  7       4h 38m 20s        Aborted (log, raw, tail)
  8       22h 43m 9s        Building (log, raw, tail)
  --------------------------------------------------

So far, these two builds alone have consumed a total of 15 days of
Hydra's build slot time.  One of the builds is on x86_64-linux and the
other on i686-linux.

As I recall, a similar thing happened with the mozjs-60 builds, although
I didn't look closely.

       Mark

  reply	other threads:[~2019-04-08  6:31 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 [this message]
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=87ef6d6mdn.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.