all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Why is this build considered a failure by hydra?
Date: Tue, 08 Apr 2014 12:16:31 +0200	[thread overview]
Message-ID: <87ppksnn28.fsf@gnu.org> (raw)
In-Reply-To: <87wqf0qz1k.fsf@yeeloong.lan> (Mark H. Weaver's message of "Mon, 07 Apr 2014 23:29:27 -0400")

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

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> ludo@gnu.org (Ludovic Courtès) skribis:
>>
>>> Offloading failed in some way.  hydra.gnunet.org was down for some time,
>>> so perhaps we hit that just at this moment.  Or some networking issue
>>> occurred just as we were retrieving the build outputs to hydra.gnu.org
>>> (although these are normally distinguished from permanent build
>>> failures, and marked as aborted.)  Or there’s a bug in the offload hook.
>>
>> A couple of days ago I fixed a possible problem: on build slaves, the GC
>> could run at the wrong moment and wipe the derivation about to be built,
>> leading to a guix build “No such file or directory” error (see commit
>> 4b00f34.)
>
> This problem is still happening.

[...]

> All of these are from the last day or two.

I fixed it when I sent the email, i.e., ~2.5 hours ago.

There’s a lot of rebuild going on now (due to OpenSSL), so I think we’ll
soon have a better idea of whether the problem still exists.

Ludo’.

      reply	other threads:[~2014-04-08 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  5:57 Why is this build considered a failure by hydra? Mark H Weaver
2014-04-03 15:14 ` Ludovic Courtès
2014-04-03 18:02   ` Andreas Enge
2014-04-05 11:01   ` Ludovic Courtès
2014-04-08  3:29     ` Mark H Weaver
2014-04-08 10:16       ` Ludovic Courtès [this message]

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=87ppksnn28.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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.