unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 27144-done@debbugs.gnu.org
Cc: 27138-done@debbugs.gnu.org
Subject: bug#27138: bug#27144: guix publish: “mutex already locked by thread”
Date: Mon, 01 Jan 2018 18:28:06 +0100	[thread overview]
Message-ID: <871sj9zdy1.fsf@gnu.org> (raw)
In-Reply-To: <87zibq3wc4.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 27 Jul 2017 14:20:27 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> Seen on hydra.gnu.org:
>>
>> GET /jkpcipgxfyfb60pr4b5n4x4j9k5mcxpp.narinfo
>> In ice-9/boot-9.scm:
>>  160: 5 [catch #t #<catch-closure 2581c20> ...]
>> In unknown file:
>>    ?: 4 [apply-smob/1 #<catch-closure 2581c20>]
>> In guix/workers.scm:
>>   84: 3 [#<procedure 2545600 at guix/workers.scm:82:2 ()>]
>>   72: 2 [loop]
>>   76: 1 [#<procedure 24a8620 at guix/workers.scm:73:11 (key . args)> misc-error ...]
>> In unknown file:
>>    ?: 0 [make-stack #t]
>> ERROR: In procedure make-stack:
>> ERROR: Throw to key `misc-error' with args `("mutex already locked by thread")'.
>>
>> This is with
>> /gnu/store/cxmj38x6rh0ykq3d5dlqbxr5h1zgiiaf-guile2.0-guix-0.13.0-1.a6d728b.
>
> My suspicion is that this is a Guile 2.0 bug (the mutex implementation
> differs from that of 2.2), and we haven’t seen it yet with Guix-on-2.2.
>
> Let’s wait a little longer and see…

I haven’t seen any such error since the original report, so I’m closing
the bug.

Ludo’.

      reply	other threads:[~2018-01-01 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 11:48 bug#27144: guix publish: “mutex already locked by thread” Ludovic Courtès
2017-07-27 12:20 ` Ludovic Courtès
2018-01-01 17:28   ` Ludovic Courtès [this message]

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=871sj9zdy1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27138-done@debbugs.gnu.org \
    --cc=27144-done@debbugs.gnu.org \
    /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).