unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: Andy Wingo <wingo@igalia.com>, guix-devel@gnu.org, 28211@debbugs.gnu.org
Subject: bug#28211: Grafting fails for latest Go release candidate
Date: Thu, 24 Aug 2017 00:53:18 +0200	[thread overview]
Message-ID: <87lgm9j3q9.fsf__27576.1277800941$1503528858$gmane$org@gnu.org> (raw)
In-Reply-To: <87wp5v2ylv.fsf@fastmail.com> (Marius Bakke's message of "Tue, 22 Aug 2017 21:26:04 +0200")

Marius Bakke <mbakke@fastmail.com> skribis:

> Most likely just lucky, new grafting failure today.
>
> I've noticed they are more likely to occur when the host system is busy.
> Grafting a large package such as 'texlive' is almost guaranteed to fail
> on a fully-utilized machine.
>
> Maybe we should switch back to 2.0 for the time being?

Yes, done: <https://bugs.gnu.org/28211>.

I took a look: the code in (guix build graft) is multi-threaded but
there’s no shared state among threads (except for the current
output/error ports, which may partly explain the error messages that
suggest memory corruption.)  So it may be that the problem is in
libguile.

Ludo’.

       reply	other threads:[~2017-08-23 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170731143925.GA19814@jasmine.lan>
     [not found] ` <87wp6kuzrp.fsf@fastmail.com>
     [not found]   ` <87wp6fb0p7.fsf@fastmail.com>
     [not found]     ` <87efsljb63.fsf@igalia.com>
     [not found]       ` <87378lszri.fsf@gnu.org>
     [not found]         ` <87h8x04qky.fsf@fastmail.com>
     [not found]           ` <87wp5v2ylv.fsf@fastmail.com>
2017-08-23 22:53             ` Ludovic Courtès [this message]
     [not found]             ` <87lgm9j3q9.fsf@gnu.org>
2017-08-24  4:56               ` bug#28211: Grafting fails for latest Go release candidate Mark H Weaver

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='87lgm9j3q9.fsf__27576.1277800941$1503528858$gmane$org@gnu.org' \
    --to=ludo@gnu.org \
    --cc=28211@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=wingo@igalia.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.
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).