all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30644@debbugs.gnu.org
Subject: bug#30644: Cuirass runs out of build users
Date: Thu, 08 Mar 2018 13:01:01 +0100	[thread overview]
Message-ID: <87efkuojya.fsf@gnu.org> (raw)
In-Reply-To: <20180308012923.525342f6@scratchpost.org> (Danny Milosavljevic's message of "Thu, 8 Mar 2018 01:29:23 +0100")

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Oops, I had an old bin/evaluate . bin/evaluate.in doesn't contain it anymore.  My bad...

Yes, see <https://bugs.gnu.org/30618>.

> Anyway, sqlite contains some cool stuff to find out who's locking it.
>
> But as things are it seems that sqlite access is now done only by one thread.  How can it then be locked?  Weird...

It’s accessed possibly from several threads because Fibers can be
thought of as an N×M threading library.

So what’s your take on this?

Ludo’.

  reply	other threads:[~2018-03-08 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  9:07 bug#30644: Cuirass runs out of build users Andreas Enge
2018-03-01 14:01 ` Ludovic Courtès
2018-03-01 20:35   ` Andreas Enge
2018-03-02 14:08 ` Efraim Flashner
2018-03-05  9:02   ` Andreas Enge
2018-03-05 15:53     ` Andreas Enge
2018-03-05 19:55       ` Andreas Enge
2018-03-07 22:35       ` Ludovic Courtès
2018-03-07 23:01         ` Danny Milosavljevic
2018-03-08  0:25           ` Danny Milosavljevic
2018-03-08  0:29             ` Danny Milosavljevic
2018-03-08 12:01               ` Ludovic Courtès [this message]
2018-03-11  6:06                 ` Danny Milosavljevic
2018-03-11 21:43                   ` Ludovic Courtès
2018-03-24 13:15                     ` Danny Milosavljevic
2018-03-25 12:40                       ` Ludovic Courtès
2021-03-25 13:17                     ` Mathieu Othacehe

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

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

  git send-email \
    --in-reply-to=87efkuojya.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30644@debbugs.gnu.org \
    --cc=dannym@scratchpost.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.