<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch debian/0.23.5-1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.23.5-1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.23.5-1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2016-12-07T11:00:40Z</updated>
<entry>
<title>cli/insert: return EX_TEMPFAIL for some errors</title>
<updated>2016-12-07T11:00:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-28T03:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d74c5345704136611f993ca38e0d035b1da798b6'/>
<id>urn:sha1:d74c5345704136611f993ca38e0d035b1da798b6</id>
<content type='text'>
Attempt to distinguish between errors indicating misconfiguration or
programmer error, which we consider "permanent", in the sense that
automatic retries are unlikely to be useful, and those indicating
transient error conditions. We consider XAPIAN_EXCEPTION transient
because it covers the important special case of locking failure.
</content>
</entry>
<entry>
<title>test: gdb insert: redirect input inside gdb script</title>
<updated>2016-12-07T11:00:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-11-28T21:07:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=27e293f653b2688fc4452a92c99e76c7e97669d1'/>
<id>urn:sha1:27e293f653b2688fc4452a92c99e76c7e97669d1</id>
<content type='text'>
Running `gdb command &lt; input` is not as reliable way to give input
to the command (some installations of gdb consume it). Use "set args"
gdb command to have input redirected at gdb 'run' time.
</content>
</entry>
<entry>
<title>tests: account for varying-size cryptographic signatures</title>
<updated>2016-11-25T00:22:12Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-11-23T17:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d31161c212368a592c5d92e3d181a986d49fcc20'/>
<id>urn:sha1:d31161c212368a592c5d92e3d181a986d49fcc20</id>
<content type='text'>
GnuPG 2.1.16 is now injecting the full issuer fingerprint in its
signatures, which makes them about 32 octets larger when
ascii-armored.

This change in size means that the size of the MIME parts will vary
depending on the version of gpg that the user has installed.  at any
rate, the signature part should be non-zero (this is true for
basically any MIME part), so we just test for that instead of an exact
size.
</content>
</entry>
<entry>
<title>test: use vt100 as "smart" terminal for known dumb/unknown terminals</title>
<updated>2016-10-22T15:18:43Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-10-20T08:19:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c008dd13523bb1356653fa8678cfe5d26a6feb82'/>
<id>urn:sha1:c008dd13523bb1356653fa8678cfe5d26a6feb82</id>
<content type='text'>
Otherwise use whatever user environment has set for TERM so
that there is more chance to test on users' actual environments.
</content>
</entry>
<entry>
<title>test-lib.sh: rename $DTACH_TERM to $SMART_TERM</title>
<updated>2016-10-22T15:13:55Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-10-20T08:19:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a3ee732c522947a17329704aef2a099946420f52'/>
<id>urn:sha1:a3ee732c522947a17329704aef2a099946420f52</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: test-lib.sh: use $BASH instead of ${SHELL-sh} to relaunch</title>
<updated>2016-09-24T13:10:40Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-09-24T12:43:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b57426a43549ac5434c0f793e184f1b0b955f7e0'/>
<id>urn:sha1:b57426a43549ac5434c0f793e184f1b0b955f7e0</id>
<content type='text'>
In case of the test script is to be relaunced under valgrind, or --tee
is requested, use the $BASH shell variable to locate the command
interpreter. The $SHELL variable is re-set by non-interactive shells
so in case the shell uses some other shell (e.g. zsh) for interactive
use these bash scripts continue to work.
</content>
</entry>
<entry>
<title>test/emacs: add broken test for message replying to msg to self</title>
<updated>2016-09-24T13:05:04Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-09-13T02:24:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5292e9b1ae60bbb66466f126463b3d6f0bf6a3b6'/>
<id>urn:sha1:5292e9b1ae60bbb66466f126463b3d6f0bf6a3b6</id>
<content type='text'>
This is a strange corner case where the removing of the user's address
from the To: header does the wrong thing. If we think it is
worth (eventually) fixing, this test can serve as a reminder.
</content>
</entry>
<entry>
<title>test: fix printf format</title>
<updated>2016-09-22T11:11:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-09-22T11:11:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1d4812fd616dbabb11eed0f3718fa7827d69355f'/>
<id>urn:sha1:1d4812fd616dbabb11eed0f3718fa7827d69355f</id>
<content type='text'>
notmuch_status_t is an integer type, printing it as a string is a very
bad idea.
</content>
</entry>
<entry>
<title>add property: query prefix to search for specific properties</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-07-08T09:15:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=693ca8d8a80438ce1e361e7e6d22288f52a11c55'/>
<id>urn:sha1:693ca8d8a80438ce1e361e7e6d22288f52a11c55</id>
<content type='text'>
We want to be able to query the properties directly, like:

   notmuch count property:foo=bar

which should return a count of messages where the property with key
"foo" has value equal to "bar".
</content>
</entry>
<entry>
<title>cli: optionally restore message properties from dump file</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=651da30c0941081cf730930fc1a7cac34954ca0e'/>
<id>urn:sha1:651da30c0941081cf730930fc1a7cac34954ca0e</id>
<content type='text'>
This somewhat mimics the config line parsing, except there can be
arbitrarily many key value pairs, so one more level of looping is
required.
</content>
</entry>
</feed>
