unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Aleksandr Vityazev <avityazew@gmail.com>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix offload
Date: Wed, 20 Dec 2023 16:08:06 +0300	[thread overview]
Message-ID: <87h6kd9g3t.fsf@gmail.com> (raw)
In-Reply-To: <b6522857-3ede-5bc3-c69b-4a7b89a31382@gmail.com> (Reza Housseini's message of "Wed, 20 Dec 2023 13:29:56 +0100")

On 2023-12-20 13:29, Reza Housseini wrote:

> On 12/20/23 12:02, Aleksandr Vityazev wrote:
>> Hello.
>> I have a configured build machine. From time to time it is not
>> available
>> and guix build gets stuck in an endless loop of:
>> guix offload: error: failed to connect to : No route to host
>> process 13902 acquired build slot
>> guix offload: error: failed to connect to : No route to host
>> process 13902 acquired build slot
>> Is it possible to make the build continue locally after several
>> unsuccessful attempts?
>
> I stumbled over the same problem and there is even an issue for this
> [1] (which looks stale). I thought maybe adding localhost as a build
> machine, but did not try it yet.

I tried the option of adding a local machine to the list, about a year
ago, the build process stuck with
/gnu/store/...compute-guix-derivation.drv

>
> Best,
> Reza
>
> [1] https://issues.guix.gnu.org/issue/24496

Thanks, didn't see that issue

-- 
Best regards,
Aleksandr Vityazev


  reply	other threads:[~2023-12-20 13:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 11:02 guix offload Aleksandr Vityazev
2023-12-20 12:29 ` Reza Housseini
2023-12-20 13:08   ` Aleksandr Vityazev [this message]
2023-12-20 15:19 ` Saku Laesvuori
2023-12-20 16:29   ` Aleksandr Vityazev
2024-02-15 16:23 ` Simon Tournier

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h6kd9g3t.fsf@gmail.com \
    --to=avityazew@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=reza.housseini@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).