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: Sun, 11 Mar 2018 22:43:48 +0100 [thread overview]
Message-ID: <87zi3ethij.fsf@gnu.org> (raw)
In-Reply-To: <20180311070610.788df5b9@scratchpost.org> (Danny Milosavljevic's message of "Sun, 11 Mar 2018 07:06:10 +0100")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Thu, 08 Mar 2018 13:01:01 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> So what’s your take on this?
>
> sqlite has a sqlite-unlock-notify. We should wrap it and use it when we get the
> "locked" error code.
>
> We should also enable extended error codes https://sqlite.org/c3ref/extended_result_codes.html .
>
> See also https://sqlite.org/unlock_notify.html for a blocking version of _step (to the right).
Interesting.
> Do we want cuirass to block until the lock is available?
The POSIX thread itself should not block. Rather the fiber should yield
to other fibers.
So we could do the blocking-step within ‘non-blocking’ block as defined
in (cuirass utils), though ‘non-blocking’ as currently implemented is a
bit expensive.
Or we could simply poll: catch those exceptions and try again later. If
this is rare enough, as seems to be the case, that might be an
acceptable approach.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2018-03-11 21:44 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
2018-03-11 6:06 ` Danny Milosavljevic
2018-03-11 21:43 ` Ludovic Courtès [this message]
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
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=87zi3ethij.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 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).