Re: Why is this build considered a failure by hydra?

[Mark H Weaver <mhw@netris.org>]

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.  Here's the most successful evaluation
we've had in a while:

  http://hydra.gnu.org/eval/66919

Here are some builds from that evaluation that failed because the
derivation had been deleted:

  http://hydra.gnu.org/build/48451 (asciidoc i686)
  http://hydra.gnu.org/build/48070 (boost i686)
  http://hydra.gnu.org/build/48516 (glib x86_64)
  http://hydra.gnu.org/build/48385 (lapack x86_64)
  http://hydra.gnu.org/build/48494 (python-setuptools x86_64)
  http://hydra.gnu.org/build/48018 (gpgme i686)
  http://hydra.gnu.org/build/48336 (libxdamage i686)
  http://hydra.gnu.org/build/48459 (libxkbfile i686)
  http://hydra.gnu.org/build/48402 (libxmu i686)
  http://hydra.gnu.org/build/47928 (mailutils i686)
  http://hydra.gnu.org/build/48511 (samba i686)
  http://hydra.gnu.org/build/47968 (shadow i686)

All of these are from the last day or two.

     Mark