unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
	Gregor Zattler <telegraph@gmx.net>,
	notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test: add known broken test for long directory bug
Date: Thu, 18 Mar 2021 09:26:43 +0200	[thread overview]
Message-ID: <m2ft0s9b2k.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20210318012509.1121007-1-david@tethera.net>

On Wed, Mar 17 2021, David Bremner wrote:

> In [1] Gregor Zattler explained the results of his hard working
> tracking down a bug in notmuch with long directories. This test
> duplicates the bug.
>
> [1]: id:20210317194728.GB5561@no.workgroup
> ---
>  test/T050-new.sh | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> diff --git a/test/T050-new.sh b/test/T050-new.sh
> index 76bda959..f84dc2b0 100755
> --- a/test/T050-new.sh
> +++ b/test/T050-new.sh
> @@ -339,6 +339,20 @@ test_expect_code 1 "NOTMUCH_NEW --debug 2>&1"
>  
>  notmuch config set new.tags $OLDCONFIG
>  
> +test_begin_subtest "Long directory names don't cause rescan"
> +test_subtest_known_broken
> +name=$(printf 'z%.0s' {1..234})

could do printf -v name 'z%.0s' {1..234}

> +generate_message [dir]=$name
> +NOTMUCH_NEW  > OUTPUT
> +notmuch new  >> OUTPUT

2 spaces in lines above

apart from those 2 spaces lgtm.

Tomi

> +rm -r ${MAIL_DIR}/${name}
> +notmuch new >> OUTPUT
> +cat <<EOF > EXPECTED
> +Added 1 new message to the database.
> +No new mail.
> +No new mail. Removed 1 message.
> +EOF
> +test_expect_equal_file EXPECTED OUTPUT
>  
>  test_begin_subtest "Xapian exception: read only files"
>  chmod u-w ${MAIL_DIR}/.notmuch/xapian/*.*
> -- 
> 2.30.2

  reply	other threads:[~2021-03-18  7:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 13:19 consistent database corruption with notmuch new Gregor Zattler
2020-12-13 14:12 ` David Bremner
2020-12-13 14:15   ` Gregor Zattler
2020-12-13 15:13     ` Gregor Zattler
2020-12-13 18:10       ` David Bremner
2020-12-13 18:12         ` David Bremner
2020-12-14 19:19           ` David Bremner
2020-12-13 21:22       ` Gregor Zattler
2020-12-14 19:22         ` Gregor Zattler
2021-01-30  8:54           ` out of memory on idle machine (was: Re: consistent database corruption with notmuch new) Gregor Zattler
2021-01-30 12:58             ` David Bremner
2021-01-31  8:16               ` out of memory on idle machine Gregor Zattler
2021-01-31 20:21                 ` Gregor Zattler
2021-02-03 11:32                   ` David Bremner
2021-02-03 11:59                 ` David Bremner
2021-02-07 21:46                   ` Gregor Zattler
2021-02-11 10:53                     ` David Bremner
2021-02-11 11:32                       ` David Bremner
2021-03-17 19:47                         ` bug: chokes on long directory names (was: Re: out of memory on idle machine) Gregor Zattler
2021-03-18  1:25                           ` [PATCH] test: add known broken test for long directory bug David Bremner
2021-03-18  7:26                             ` Tomi Ollila [this message]
2021-03-18 11:02                               ` David Bremner
2021-03-20 13:10                             ` [PATCH] lib/n_d_index_file: check return value from _n_m_add_filename David Bremner
2021-04-18 13:05                               ` David Bremner
2021-03-18  1:39                           ` bug: chokes on long directory names (was: Re: out of memory on idle machine) David Bremner
2021-02-12  4:19                       ` out of memory on idle machine Olly Betts
2021-02-21  9:42                         ` Gregor Zattler
2021-02-09  4:34                   ` Olly Betts
2021-02-13 20:30                     ` Gregor Zattler
2020-12-14  9:11 ` consistent database corruption with notmuch new David Edmondson
2020-12-14 12:27   ` Gregor Zattler

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=m2ft0s9b2k.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=telegraph@gmx.net \
    /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).