diff options
| author | David Bremner <david@tethera.net> | 2017-08-27 20:58:21 -0300 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2017-09-05 21:51:21 -0300 |
| commit | 36a3d65034f1aa8de77c21013c63f0198aef386c (patch) | |
| tree | 91f4110c4cad9797acff1f4354497b13fccf8bba /test | |
| parent | 17aebb6e7d18adc85c64e6e716cef6f01f3113f4 (diff) | |
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
Diffstat (limited to 'test')
| -rwxr-xr-x | test/T670-duplicate-mid.sh | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/test/T670-duplicate-mid.sh b/test/T670-duplicate-mid.sh index d2f89432..d4c1d1c2 100755 --- a/test/T670-duplicate-mid.sh +++ b/test/T670-duplicate-mid.sh @@ -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 | |