unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test/emacs: known broken test for matching fcc and sent message
Date: Fri, 21 Jan 2022 07:37:49 -0400	[thread overview]
Message-ID: <87tudxfhf6.fsf@tethera.net> (raw)
In-Reply-To: <m2r192awzq.fsf@guru.guru-group.fi>

Tomi Ollila <tomi.ollila@iki.fi> writes:

> On Wed, Jan 19 2022, David Bremner wrote:
>
>> David Bremner <david@tethera.net> writes:
>>
>>> Based on the method outlined by Daniel Kahn Gilmour in
>>> id:87k1zm225v.fsf@fifthhorseman.net.  With a delay of 0.2 seconds the
>>> test becomes flaky on my machine. With a 1 second delay it fails
>>> consistently for more than 1600 iterations.
>>
>> And yet I didn't test the next test in the file, which I broke by adding
>> another signed message. This is fixed in git.
>
> I don't see commit im my pull (if that meant it, so probably only in your
> own git) -- so you have chance to fix typo in the commit message :D
>

Ah, I see the typo now. Once more proving, never type what you can
copy-pasta.

d

  parent reply	other threads:[~2022-01-21 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 23:28 BUG: emacs: fcc duplicates messages with variant bodies due to mml security Daniel Kahn Gillmor
2022-01-19 13:56 ` David Bremner
2022-01-20  2:44   ` [PATCH] test/emacs: known broken test for matching fcc and sent message David Bremner
2022-01-20  3:02     ` David Bremner
2022-01-20 22:00       ` Tomi Ollila
2022-01-21  0:21         ` David Bremner
2022-01-21 11:37         ` David Bremner [this message]
2022-01-26 11:55 ` BUG: emacs: fcc duplicates messages with variant bodies due to mml security 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=87tudxfhf6.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).