<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T560-lib-error.sh, branch 0.22.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.22.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.22.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2016-04-12T23:21:09Z</updated>
<entry>
<title>test: cope with glass backend file naming variations</title>
<updated>2016-04-12T23:21:09Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-04-09T01:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e311aad182326a1dcb0f8512e10b0e0f0faa9e2c'/>
<id>urn:sha1:e311aad182326a1dcb0f8512e10b0e0f0faa9e2c</id>
<content type='text'>
In several places in the test suite we intentionally corrupt the Xapian
database in order to test error handling. This corruption is specific to
the on-disk organization of the database, and that changed with the
glass backend. We use the previously computed default backend to make
the tests adapt to changing names.
</content>
</entry>
<entry>
<title>test: improve error handling in lib-error tests</title>
<updated>2016-04-12T23:04:03Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-04-09T01:49:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=45df509cb6fd642bc5895f2c7869a354c1255f4b'/>
<id>urn:sha1:45df509cb6fd642bc5895f2c7869a354c1255f4b</id>
<content type='text'>
There is at least one bug fixed here (missing parameter to printf), even
if exiting via segfault is considered OK.
</content>
</entry>
<entry>
<title>test: refactor directory name sanitization</title>
<updated>2016-01-27T02:50:58Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-01-23T12:49:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=12534d5c4b02498173b0c63d063ae0a3c845b957'/>
<id>urn:sha1:12534d5c4b02498173b0c63d063ae0a3c845b957</id>
<content type='text'>
test_C and notmuch_search_files_sanitize were giving different output on
the same path, which is not technically wrong, but slightly
confusing.
</content>
</entry>
<entry>
<title>test: move backup_database and restore_database to library</title>
<updated>2015-09-04T11:22:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-06-07T15:01:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9ee29ad6f0805dc55e63f8a04a68a1f55d0c382b'/>
<id>urn:sha1:9ee29ad6f0805dc55e63f8a04a68a1f55d0c382b</id>
<content type='text'>
The plan is to re-use them in testing the same errors from the CLI
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
<entry>
<title>lib: reject relative paths in n_d_{create,open}_verbose</title>
<updated>2015-06-12T05:34:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-06-08T06:02:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=32fd74b7aa9c24ec77f8c59d09f89e0535bf64cd'/>
<id>urn:sha1:32fd74b7aa9c24ec77f8c59d09f89e0535bf64cd</id>
<content type='text'>
There are many places in the notmuch code where the path is assumed to be absolute. If someone (TM) wants a project, one could remove these assumptions. In the mean time, prevent users from shooting themselves in the foot.

Update test suite mark tests for this error as no longer broken, and
also convert some tests that used relative paths for nonexistent
directories.
</content>
</entry>
<entry>
<title>lib: add NOTMUCH_STATUS_PATH_ERROR</title>
<updated>2015-06-12T05:34:47Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-06-10T05:58:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b59ad1a9cc6ea03764b1cd3d038920581ac5a9c4'/>
<id>urn:sha1:b59ad1a9cc6ea03764b1cd3d038920581ac5a9c4</id>
<content type='text'>
The difference with FILE_ERROR is that this is for things that are
wrong with the path before looking at the disk.

Add some 3 tests; two broken as a reminder to actually use this new
code.
</content>
</entry>
<entry>
<title>test: move nonexistent directory to something under notmuch's control.</title>
<updated>2015-04-08T14:43:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-04-07T12:10:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=294bb6de20de7d9c83a45dca22888d557ece588a'/>
<id>urn:sha1:294bb6de20de7d9c83a45dca22888d557ece588a</id>
<content type='text'>
Apparently some systems actually have a directory called /nonexist[ae]nt.
It's hard to fathom a good reason for that, but oh well. As long as we
don't create such a directory inside the notmuch source tree, the new
version should be more robust.
</content>
</entry>
<entry>
<title>test: be consistent about spelling `nonexistent'</title>
<updated>2015-04-08T14:43:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-04-08T14:31:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2e9ecb611a7f698808add756b2ddcbdfcd8b7c8b'/>
<id>urn:sha1:2e9ecb611a7f698808add756b2ddcbdfcd8b7c8b</id>
<content type='text'>
Apparently most of the misspellings are my fault.
</content>
</entry>
<entry>
<title>test: make one error output test more robust.</title>
<updated>2015-03-29T07:50:01Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-03-29T07:39:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=703c8f9511c6f96023fb180b0e9d831e762befc9'/>
<id>urn:sha1:703c8f9511c6f96023fb180b0e9d831e762befc9</id>
<content type='text'>
Since notmuch_database_status_string can return NULL, passing it
directly to fputs is not a good idea.
</content>
</entry>
</feed>
