<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T070-insert.sh, branch 0.23.5</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.23.5</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.23.5'/>
<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>test: make gdb even quieter</title>
<updated>2016-08-09T00:33:59Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-28T21:08:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f45fa5bdd397d52473f7092f7ae3e2ffb9b7aee5'/>
<id>urn:sha1:f45fa5bdd397d52473f7092f7ae3e2ffb9b7aee5</id>
<content type='text'>
gdb sometimes writes warnings to stdout, which we don't need/want, and
for some reason --batch-silent isn't enough to hide. So in this commit
we write them to a log file, which is probably better for debugging
anyway. To see an illustrative test failure before this change, run

% make
% touch notmuch-count.c
% cd test &amp;&amp; ./T060-count.sh
</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: 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: remove redundant 'file' command from gdb scripts.</title>
<updated>2015-05-31T16:56:10Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-05-31T16:56:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5df1b1bb81b1983578e636ac62000e280d241139'/>
<id>urn:sha1:5df1b1bb81b1983578e636ac62000e280d241139</id>
<content type='text'>
Quoting Debian bug 787341

   It failed to build on arm64: the last ten tests in T070-insert
   failed.

   What's happening here is that GDB is segfaulting in response to
   the
   "file" command. GDB on arm64 can be a bit buggy.

   However, the "file" command is redundant here as GDB has already
   got
   the file from the --args on the command line.
</content>
</entry>
<entry>
<title>test: check for gdb in insert tests</title>
<updated>2014-10-18T06:13:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-10-18T06:13:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dd8373fb571f93cf3bf824777e00278979ef2e21'/>
<id>urn:sha1:dd8373fb571f93cf3bf824777e00278979ef2e21</id>
<content type='text'>
Commits a6cee01 and c48b12f otherwise break the build for people
without gdb.
</content>
</entry>
<entry>
<title>test/insert: check that indexing errors are accepted with --keep</title>
<updated>2014-10-18T05:58:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-10-03T21:19:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c48b12f18a4b9e0b46ec40ad7bab19a8086493fd'/>
<id>urn:sha1:c48b12f18a4b9e0b46ec40ad7bab19a8086493fd</id>
<content type='text'>
This is overkill for the current code path, but should provide some
robustness for future changes in error handling.
</content>
</entry>
<entry>
<title>cli/insert: require succesful message indexing for success status</title>
<updated>2014-10-18T05:54:25Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-10-03T21:18:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dc20a0eedc80477c0db7b7dea9efef90860ec9fb'/>
<id>urn:sha1:dc20a0eedc80477c0db7b7dea9efef90860ec9fb</id>
<content type='text'>
Add --keep option to keep any remaining stuff in index or file. We
could distinguish between failures to index and failures to apply tags
or maildir sync, but for simplicity just have one.
</content>
</entry>
<entry>
<title>test/insert: add known broken tests for indexing failures</title>
<updated>2014-10-18T05:51:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-10-03T21:18:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a6cee01b4e537e22b008f838d4af4e9d2f012f22'/>
<id>urn:sha1:a6cee01b4e537e22b008f838d4af4e9d2f012f22</id>
<content type='text'>
These tests are written with the assumption that we want all indexing
failures to be considered as failures by notmuch insert.
</content>
</entry>
</feed>
