From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Artyom Poptsov <poptsov.artyom@gmail.com>, 26976-done@debbugs.gnu.org
Subject: bug#26976: On Hydra, offload crashes while trying to build linux-libre source
Date: Thu, 27 Jul 2017 12:14:26 +0200 [thread overview]
Message-ID: <87eft25gql.fsf@gnu.org> (raw)
In-Reply-To: <87shj3tvzd.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 13 Jun 2017 23:32:06 +0200")
Hello,
ludo@gnu.org (Ludovic Courtès) skribis:
> I’ve pushed a workaround that seems to work (‘guix copy’ commands that
> previously segfaulted on hydra.gnu.org no longer do):
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8e469b67f95cfe5b95405b503b8ee315fdf8ce66
The workaround has proved to work well for ‘guix offload’ and ‘guix
copy’ so I’m closing this bug on our side.
In Guile-SSH though, I think there’s still the potential for finalizers
getting called in a separate thread and triggering the issue we’ve seen
here. Am I right, Artyom?
If I’m not mistaken, that calls for a fix as described in
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26976#37>, namely
protecting libssh objects with mutexes.
Ludo’.
next prev parent reply other threads:[~2017-07-27 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 1:55 bug#26976: On Hydra, offload crashes while trying to build linux-libre source Mark H Weaver
2017-05-18 2:02 ` Mark H Weaver
2017-05-18 22:00 ` Ludovic Courtès
2017-05-19 3:20 ` Artyom Poptsov
2017-05-19 12:44 ` Ludovic Courtès
2017-05-19 22:36 ` Ludovic Courtès
2017-05-20 21:59 ` Ludovic Courtès
2017-06-05 21:33 ` Ludovic Courtès
2017-06-13 21:32 ` Ludovic Courtès
2017-06-14 20:10 ` Ludovic Courtès
2017-07-27 10:14 ` Ludovic Courtès [this message]
2017-05-20 16:59 ` Mark H Weaver
2017-05-20 18:02 ` Ludovic Courtès
2017-05-20 22:21 ` Ludovic Courtès
2017-06-14 6:58 ` Mark H Weaver
2017-06-14 7:15 ` 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=87eft25gql.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26976-done@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=poptsov.artyom@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.
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).