From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] test: don't use dump and restore in a pipeline
Date: Wed, 29 Jun 2016 09:09:42 +0200 [thread overview]
Message-ID: <87furw1nex.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <1467102247-27791-1-git-send-email-david@tethera.net>
David Bremner <david@tethera.net> writes:
> This has been wrong since bbbdf0478ea, but the race condition was not
> previously been (often?) triggered in the tests. With the DB_RETRY_LOCK
> patches, it manifests itself as a deadlock.
pushed, to prepare for the DB_RETRY_LOCK patches
prev parent reply other threads:[~2016-06-29 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 8:24 [PATCH] test: don't use dump and restore in a pipeline David Bremner
2016-06-29 7:09 ` David Bremner [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87furw1nex.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).