mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-21 18:38:08 +01:00
test: known broken test for subject after reindexing
In [1], Mark gave a test that was behaving strangly. This turns out to be specific to reindexing. I suppose one could argue that picking the lexicographically last file name is a defensible choice, but it's almost as easy to take the first, which seems more intuitive. So mark the current situation as broken. [1]: id:1503859703-2973-1-git-send-email-markwalters1009@gmail.com
This commit is contained in:
parent
17aebb6e7d
commit
36a3d65034
1 changed files with 8 additions and 0 deletions
|
@ -40,6 +40,14 @@ notmuch reindex '*'
|
|||
notmuch search --output=files "sekrit" | notmuch_dir_sanitize > OUTPUT
|
||||
test_expect_equal_file EXPECTED OUTPUT
|
||||
|
||||
test_begin_subtest 'reindex choses subject from first filename'
|
||||
test_subtest_known_broken
|
||||
cat <<EOF > EXPECTED
|
||||
thread:XXX 2001-01-05 [1/1(3)] Notmuch Test Suite; message 0 (inbox unread)
|
||||
EOF
|
||||
notmuch search id:duplicate | notmuch_search_sanitize > OUTPUT
|
||||
test_expect_equal_file EXPECTED OUTPUT
|
||||
|
||||
rm ${MAIL_DIR}/copy0
|
||||
test_begin_subtest 'Deleted first duplicate file does not stop notmuch show from working'
|
||||
output=$(notmuch show --body=false --format=json id:duplicate |
|
||||
|
|
Loading…
Reference in a new issue