From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Cc: David Bremner <david@tethera.net>
Subject: Re: [PATCH] test: add known broken test for duplicate thread-id terms
Date: Mon, 17 May 2021 10:12:31 +0300 [thread overview]
Message-ID: <m2pmxp7s0w.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20210515130507.2629859-1-david@tethera.net>
On Sat, May 15 2021, David Bremner wrote:
> According to my bijection, this bug has been present since commit
> 411675a6ce in 2017. It is apparently harmless for regular use, but
> does make notmuch crash when compiled with -DDEBUG_DATABASE_SANITY.
> ---
> test/T670-duplicate-mid.sh | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/test/T670-duplicate-mid.sh b/test/T670-duplicate-mid.sh
> index 4e5672ab..3fd59ca5 100755
> --- a/test/T670-duplicate-mid.sh
> +++ b/test/T670-duplicate-mid.sh
> @@ -2,10 +2,27 @@
> test_description="duplicate message ids"
> . $(dirname "$0")/test-lib.sh || exit 1
>
> +test_require_external_prereq xapian-delve
> +
> add_message '[id]="duplicate"' '[subject]="message 1" [filename]=copy1'
> add_message '[id]="duplicate"' '[subject]="message 2" [filename]=copy2'
>
> add_message '[id]="duplicate"' '[subject]="message 0" [filename]=copy0'
> +
> +test_begin_subtest 'at most 1 thread-id per xapian document'
> +test_subtest_known_broken
> +db=${MAIL_DIR}/.notmuch/xapian
> +cp /dev/null OUTPUT.raw
> +for doc in $(xapian-delve -1 -t '' "$db" | grep '^[1-9]'); do
> + xapian-delve -1 -r "$doc" "$db" | grep '^G' | wc -l >> OUTPUT.raw
> +done
for doc in $(xapian-delve -1 -t '' "$db" | grep '^[1-9]'); do
xapian-delve -1 -r "$doc" "$db" | grep -c '^G'
done > OUTPUT.raw
will do (w/o cp /dev/null OUTPUT.raw) (also NOTE SPACING !!! >;D)
> +sort -u < OUTPUT.raw > OUTPUT
> +cat <<EOF > EXPECTED
> +0
> +1
> +EOF
> +test_expect_equal_file EXPECTED OUTPUT
> +
> test_begin_subtest 'search: first indexed subject preserved'
> cat <<EOF > EXPECTED
> thread:XXX 2001-01-05 [1/1(3)] Notmuch Test Suite; message 1 (inbox unread)
> --
> 2.30.2
next prev parent reply other threads:[~2021-05-17 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 13:05 [PATCH] test: add known broken test for duplicate thread-id terms David Bremner
2021-05-15 18:40 ` [PATCH] lib/n_d_index_file: re-use thread-id of existing message David Bremner
2021-05-17 7:12 ` Tomi Ollila [this message]
2021-05-17 9:33 ` [PATCH] test: add known broken test for duplicate thread-id terms Michael J Gruber
2021-05-17 10:02 ` David Bremner
2021-05-22 12:40 ` 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=m2pmxp7s0w.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=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).