<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch debian/bookworm-backports</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fbookworm-backports</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fbookworm-backports'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2023-09-23T11:34:48Z</updated>
<entry>
<title>Pass error message from GLib ini parser to CLI</title>
<updated>2023-09-23T11:34:48Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-09-15T12:50:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c10d91d8e4a3e5bc76ca4c6b9939f3759e6ef5e'/>
<id>urn:sha1:1c10d91d8e4a3e5bc76ca4c6b9939f3759e6ef5e</id>
<content type='text'>
The function _notmuch_config_load_from_file is only called in two
places in open.cc. Update internal API to match the idiom in open.cc.
Adding a newline is needed for consistency with other status strings.

Based in part on a patch [1] from Eric Blake.

[1]: id:20230906153402.101471-1-eblake@redhat.com
</content>
</entry>
<entry>
<title>test: add known broken subtest for the bad config error message</title>
<updated>2023-09-23T11:29:32Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-09-15T12:50:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bc38580cef3316254b1ffb15b4711b541c6f9bb3'/>
<id>urn:sha1:bc38580cef3316254b1ffb15b4711b541c6f9bb3</id>
<content type='text'>
This is a bit fragile w.r.t. glib changing their error message, but it
already helped me find one formatting bug, so for now I think it's
worth it, instead of just grepping for "UTF-8".
</content>
</entry>
<entry>
<title>CLI: exit with error when load_config returns an error.</title>
<updated>2023-09-23T11:26:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-09-15T12:50:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dbb5ff338511bfa6718ed144b95a689809d4bea1'/>
<id>urn:sha1:dbb5ff338511bfa6718ed144b95a689809d4bea1</id>
<content type='text'>
For now print a generic error message and exit with error on any
non-success code. Previously the code exited, but with exit code zero,
leading users / scripts to think the command had succeeded.
</content>
</entry>
<entry>
<title>test: add known broken test for bad utf8 in config</title>
<updated>2023-09-23T11:22:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-09-15T12:50:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=112c53535a569ba28a2a7f3baae7fcc4033c65bc'/>
<id>urn:sha1:112c53535a569ba28a2a7f3baae7fcc4033c65bc</id>
<content type='text'>
We should ideally print an informative error message, but at the very
least we should not exit with success.
</content>
</entry>
<entry>
<title>test: minimize impact of native compilation.</title>
<updated>2023-08-26T10:45:36Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-08-26T10:45:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=115d4d69ebbab213baae672ac4e81947877f364b'/>
<id>urn:sha1:115d4d69ebbab213baae672ac4e81947877f364b</id>
<content type='text'>
Native compilation is kindof useless in the test suite because we
throw away the cache after every subtest.  The test suite could in
principle share an eln cache within a given test file; for now try to
minimize the amount of native-compilation. There is an intermittent
bug where emacs loses track of its default-directory; I suspect (but
have no proof) that bug is related to native compilation and/or race
conditions. This patch seems to prevent that bug (or at least reduce
its frequency).
</content>
</entry>
<entry>
<title>test/setup: ignore blank lines in generated config</title>
<updated>2023-08-21T22:30:54Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-08-20T15:23:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=368e0f61d5498ceae180e8349e848a4904008b0b'/>
<id>urn:sha1:368e0f61d5498ceae180e8349e848a4904008b0b</id>
<content type='text'>
The presense of the blank lines between sections depends on the
version of glib. Strip them before comparison.
</content>
</entry>
<entry>
<title>test/emacs: adapt to breaking change in Gnus defaults</title>
<updated>2023-08-20T17:32:02Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-08-20T17:32:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1719b9e568fb944ffb91126b164a18a30a415d0a'/>
<id>urn:sha1:1719b9e568fb944ffb91126b164a18a30a415d0a</id>
<content type='text'>
As of Emacs 29.1, In-Reply-To is in the default value for
message-hidden-headers. We actually want to see that in the test
suite, so remove it again. To future proof the tests, fix a default
value for message-hidden-headers specifically for the test suite.
</content>
</entry>
<entry>
<title>test: support testing notmuch as installed</title>
<updated>2023-07-21T10:41:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ec26eeaeec87781dee7dbf720103a5bc9b6bba5d'/>
<id>urn:sha1:ec26eeaeec87781dee7dbf720103a5bc9b6bba5d</id>
<content type='text'>
We put some effort into testing the built copy rather than some
installed copy. On the other hand for people like packagers, testing
the installed copy is also of interest.

When NOTMUCH_TEST_INSTALLED is set to a nonempty value, tests do not
require a built notmuch tree or running configure.

Some of the tests marked as broken when running against installed
notmuch are probably fixable.
</content>
</entry>
<entry>
<title>test: Guess a value for NOTMUCH_PYTHON</title>
<updated>2023-07-21T10:07:43Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=73f3081160fb80345f3953cbdeba340975375325'/>
<id>urn:sha1:73f3081160fb80345f3953cbdeba340975375325</id>
<content type='text'>
python3 will work for many people, and reduce the friction to running
the tests without running configure first.
</content>
</entry>
<entry>
<title>test: check for empty/missing files in test_expect_equal_message_body</title>
<updated>2023-07-21T10:07:43Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f6fcdf12da455d82a9ed0a0a33eddac60253a6e8'/>
<id>urn:sha1:f6fcdf12da455d82a9ed0a0a33eddac60253a6e8</id>
<content type='text'>
Messages can have empty bodies, but empty files are not messages.
</content>
</entry>
</feed>
