]> git.notmuchmail.org Git - notmuch/commitdiff
test: Drop test for propagating flag changes from one file to another
authorCarl Worth <cworth@cworth.org>
Thu, 11 Nov 2010 11:43:09 +0000 (03:43 -0800)
committerCarl Worth <cworth@cworth.org>
Thu, 11 Nov 2010 11:47:11 +0000 (03:47 -0800)
There's nothing in the current API documentation that would suggest
the behavior being tested here. Attempt to implement this could have
some nasty side effects, (such as notmuch_message_maildir_flags_to_tags
implicitly calling notmuch_message_tags_to_maildir_flags and maybe
even opening up some bad looping possibilities).

Much better to stick with what we have documented, which we believe will
actually be useful, (and easy enough to comprehend).

test/maildir-sync

index 5984f54296bd66aa9207ecf86e246ec76475111a..363534aa2f368ea8e13e5fca78e0305f11dee339 100755 (executable)
@@ -155,11 +155,6 @@ notmuch search subject:"Duplicated message" | notmuch_search_sanitize >> output
 test_expect_equal "$(< output)" "No new mail.
 thread:XXX   2001-01-05 [1/1] Notmuch Test Suite; Duplicated message (inbox replied)"
 
 test_expect_equal "$(< output)" "No new mail.
 thread:XXX   2001-01-05 [1/1] Notmuch Test Suite; Duplicated message (inbox replied)"
 
-test_begin_subtest "Duplicate mail with new flags propagates flag to original file"
-(cd $MAIL_DIR/cur/; ls duplicated*) > actual
-test_expect_equal "$(< actual)" "duplicated-message:2,RS
-duplicated-message-copy:2,RS"
-
 test_begin_subtest "Adding duplicate message without flags does not remove tags"
 cp "$MAIL_DIR/cur/duplicated-message-copy:2,RS" "$MAIL_DIR/cur/duplicated-message-another-copy:2,"
 increment_mtime $MAIL_DIR/cur
 test_begin_subtest "Adding duplicate message without flags does not remove tags"
 cp "$MAIL_DIR/cur/duplicated-message-copy:2,RS" "$MAIL_DIR/cur/duplicated-message-another-copy:2,"
 increment_mtime $MAIL_DIR/cur