From: David Bremner <david@tethera.net>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH] test: Fix transient error in 'new' test
Date: Tue, 24 Dec 2013 20:52:57 +0900 [thread overview]
Message-ID: <871u12xy7a.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <1387830036-16434-1-git-send-email-amdragon@mit.edu>
Austin Clements <amdragon@MIT.EDU> writes:
> This patch fixes this problem by touching ${MAIL_DIR} to ensure it
> gets scanned and by rearranging the test to ensure the directories are
> touched immediately before the main notmuch new call in the test
This update seems to make the test reliable for me (roughly 20k
iterations).
d
next prev parent reply other threads:[~2013-12-24 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 1:06 one more intermittent test failure David Bremner
2013-12-23 20:20 ` [PATCH] test: Fix transient error in 'new' test Austin Clements
2013-12-24 11:52 ` David Bremner [this message]
2013-12-29 3:20 ` David Bremner
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=871u12xy7a.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=amdragon@MIT.EDU \
--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).