unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 42053@debbugs.gnu.org
Subject: bug#42053: hidden derivation build with inferiors
Date: Fri, 26 Jun 2020 12:17:28 +0200	[thread overview]
Message-ID: <87mu4qnnbb.fsf@gnu.org> (raw)
In-Reply-To: <20200626014712.5620ac06@tachikoma.lepiller.eu> (Julien Lepiller's message of "Fri, 26 Jun 2020 01:47:12 +0200")

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

> someone (kernel-help) on IRC today was having issues using an inferior
> kernel with their os configuration and reported that guix was
> "hanging". It turns out that guix was actually building the kernel in
> the background, but did not report anything to the user. kernel-help
> was kind enough to share their config, and I can confirm that guix is
> building the kernel, but doesn't tell anything.

Aaah right.  What happens here is that grafts lead the inferior to start
building the kernel (this is expected).  However, ‘proxy’ in (guix
inferior) doesn’t forward build output to ‘current-build-output-port’.
That’s why there’s no message saying what’s being built, no spinner, etc.

I’ll see what can be done.

The problem has always been there but it was perhaps less visible before
710854304b1ab29332edcb76f3de532e0724c197, at least when substitutes were
available, because then the inferior wouldn’t start building things.

Ludo’.




  reply	other threads:[~2020-06-26 10:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 23:47 bug#42053: hidden derivation build with inferiors Julien Lepiller
2020-06-26 10:17 ` Ludovic Courtès [this message]
2020-06-26 10:19   ` Julien Lepiller
2020-06-26 12:08     ` Ludovic Courtès
2020-06-28 20:43   ` Ludovic Courtès

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=87mu4qnnbb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=42053@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).