<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch debian/0.17-1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.17-1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.17-1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-12-28T13:19:51Z</updated>
<entry>
<title>test: Fix transient error in 'new' test</title>
<updated>2013-12-28T13:19:51Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-12-23T20:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ef7b77ea3b1b23d29af3f0d8d9393b94b3ada993'/>
<id>urn:sha1:ef7b77ea3b1b23d29af3f0d8d9393b94b3ada993</id>
<content type='text'>
This fixes a non-deterministic failure in "Ignore files and
directories specified in new.ignore (multiple occurrences)".  The test
assumed that all directories would be scanned, even though nothing
updated the mtime of ${MAIL_DIR}.  It *usually* worked nevertheless
because the tests run quickly enough that the directory mtime is
usually the same as the current time, so notmuch new does not update
the mtime in the database (because more changes could occur in the
same second).  However, when it occasionally did update the mtime in
the database, the notmuch new call in this test would (correctly) skip
"pass 2" of scanning ${MAIL_DIR}, causing it to skip the following
expected lines:

  (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/.git
  (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/.ignored_hidden_file
  (D) add_files_recursive, pass 2: explicitly ignoring ${MAIL_DIR}/ignored_file

This patch fixes this problem by touching ${MAIL_DIR} to ensure it
gets scanned and by rearranging the test to ensure the directories are
touched immediately before the main notmuch new call in the test.
</content>
</entry>
<entry>
<title>test: remove call to notmuch-hello from emacs_deliver_message</title>
<updated>2013-12-22T12:44:45Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-14T14:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=30cde97ba87d7eb60ce4b0aa1c60d0ee6487fac9'/>
<id>urn:sha1:30cde97ba87d7eb60ce4b0aa1c60d0ee6487fac9</id>
<content type='text'>
There is an obscure bug in notmuch-hello that very occasionally causes
emacs_deliver_message to fail. Since it it doesn't serve any actual
purpose in the function we delete it, and leave tracking down the the
bug for another day.
</content>
</entry>
<entry>
<title>test: add emacs_fcc_message that does not use smtp-dummy</title>
<updated>2013-12-22T12:44:44Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-14T14:39:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=513a36d105995c327c23fec5f60ea70c65b986dd'/>
<id>urn:sha1:513a36d105995c327c23fec5f60ea70c65b986dd</id>
<content type='text'>
Most of the tests previously using emacs_deliver_message do not use
the actual transmitted message, so we replace it with a simpler (and
presumably more reliable function) that only saves (and indexes) an
fcc copy of the message.
</content>
</entry>
<entry>
<title>test: give unique timestamps to messages</title>
<updated>2013-12-09T13:20:28Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T15:29:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b421f00a05dba82d6c3df6dcb6ae9063c5395b49'/>
<id>urn:sha1:b421f00a05dba82d6c3df6dcb6ae9063c5395b49</id>
<content type='text'>
The choice of decreasing timestamps is a hack which reduces the number
of existing tests which fail.  This can be changed to increasing
if/when somebody wants update another 47 tests.
</content>
</entry>
<entry>
<title>test: sanitize dates in emacs, raw, and text output</title>
<updated>2013-12-09T13:20:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T14:52:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=72ff135ac3e79be548bf5b82b63d15ba278ef4ce'/>
<id>urn:sha1:72ff135ac3e79be548bf5b82b63d15ba278ef4ce</id>
<content type='text'>
add a new function notmuch_date_sanitize for rfc822-ish things. Add
date sanitization to notmuch_show_sanitize_all and use it more places.

This is all in aid of a transition to unique timestamps on messages.
</content>
</entry>
<entry>
<title>test: sanitize Date and timestamp fields in json</title>
<updated>2013-12-09T13:20:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T08:41:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=18921be2e9c0b15c7a4c053718470f667fd35b35'/>
<id>urn:sha1:18921be2e9c0b15c7a4c053718470f667fd35b35</id>
<content type='text'>
Eventually we want test messages to have distinct dates to avoid
reproducability problems. This sanitization will prevent some test
failures when that change is made.

Replace the use of a local function in maildir-sync with
notmuch_json_show_sanitize
</content>
</entry>
<entry>
<title>test: pass expected output through json_sanitize in 2 places</title>
<updated>2013-12-09T13:20:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T08:39:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=20f78709faae8fb36c6ebbf81ecfc856a5dcd3c7'/>
<id>urn:sha1:20f78709faae8fb36c6ebbf81ecfc856a5dcd3c7</id>
<content type='text'>
This makes the tests more robust against changes in the
sanitization rules.
</content>
</entry>
<entry>
<title>test/crypto: disable gpg version printing</title>
<updated>2013-11-28T11:02:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-11-27T15:35:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=456799d514473187758f51c0569b0676575db978'/>
<id>urn:sha1:456799d514473187758f51c0569b0676575db978</id>
<content type='text'>
This was causing test failures because version strings varied in
length between GNU/Linux and GNU/KFreeBSD. One can also imagine
different versions of gnupg causing the same failure.
</content>
</entry>
<entry>
<title>test: replace $PWD with YYY in emacs &amp; emacs-show tests</title>
<updated>2013-11-24T00:25:29Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-11-23T11:01:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2560996b7ebb08cca7e20fbb182998bc2e0e2151'/>
<id>urn:sha1:2560996b7ebb08cca7e20fbb182998bc2e0e2151</id>
<content type='text'>
When executed command line is written to *Notmuch errors* buffer,
shell-quote-argument will backslash-escape any char that is not in
"POSIX filename characters" (i.e. matching "[^-0-9a-zA-Z_./\n]").

Currently in two emacs tests shell has expanded $PWD as part of
emacs variable, which will later be fed to #'shell-quote-argument
and finally written to ERROR file. If $PWD contained non-POSIX
filename characters, data in ERROR file will not match $PWD when
later comparing in shell. Therefore, in these two particular cases
the escaped $PWD is replaced with YYY in ERROR file and expected
content is adjusted accordingly.
</content>
</entry>
<entry>
<title>emacs: Fix search tagging races</title>
<updated>2013-11-09T00:52:00Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-10-24T15:19:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=96c0ce28f8288773870bff5a6ef1c43ff3a931f8'/>
<id>urn:sha1:96c0ce28f8288773870bff5a6ef1c43ff3a931f8</id>
<content type='text'>
This fixes races in thread-local and global tagging in notmuch-search
(e.g., "+", "-", "a", "*", etc.).  Previously, these would modify tags
of new messages that arrived after the search.  Now they only operate
on the messages that were in the threads when the search was
performed.  This prevents surprises like archiving messages that
arrived in a thread after the search results were shown.

This eliminates `notmuch-search-find-thread-id-region(-search)'
because these functions strongly encouraged racy usage.

This fixes the two broken tests added by the previous patch.
</content>
</entry>
</feed>
