notmuch/test/T560-lib-error.sh, branch 0.31.4 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.31.4 2020-08-01T23:27:30Z test: drop use of db_ending 2020-08-01T23:27:30Z David Bremner david@tethera.net 2020-07-30T00:01:30Z urn:sha1:99a7aac8f2af6f3adb8f816be46ee33eb1d57515 This will allow the dropping of the test for the default ending from configure. test: move notmuch_message_* tests to their own file 2020-07-29T15:18:11Z David Bremner david@tethera.net 2020-07-22T10:51:18Z urn:sha1:85da95e26699a404b3bb3e1c01ea7998a1284abd This is for consistency with the recently added tests for notmuch_database_*. lib: rename _n_d_create to _n_d_find_or_create 2020-07-22T22:52:55Z David Bremner david@tethera.net 2020-07-19T10:36:47Z urn:sha1:ce360ce4c99597946949317aa40892536c9ebc05 The error message and name were confusing when called in some "read only" context. lib: fix exception messages for n_m_message_* 2020-07-22T22:52:55Z David Bremner david@tethera.net 2020-07-22T11:19:28Z urn:sha1:e9867b818b75216427c7190f67354959dfb914db The original generic handler had an extra '%s' in the format string. Update tests that failed to catch this because the template to print status strings checked 'stat', which was not set. lib: fix return value for n_m_reindex 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:09Z urn:sha1:765ca7bc08f83a3c0f9ebffe58dab03634e45f37 Also update the documentation for the behaviour of n_m_get_thread_id that this fix relies on. test: add known broken test for n_m_reindex on closed db 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:08Z urn:sha1:a0c83e1fac88588ff6564dd82fbca29c2f5c78a5 This is another case where the code should not call INTERNAL_ERROR. test: regression for retrieving closed db from message 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:07Z urn:sha1:a2279c322e65ff26a136a2fb801a1d0670a45c69 This is actually one of the few potentially useful things you can do with a message belonging to a closed database, since in principle you could re-open the database. test: regression test for destroying message with closed db 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:06Z urn:sha1:1578e2af6a412a72346d5264d2d6707972a95b33 This should be fine because the message belongs to the database (talloc context wise). test: regression tests of n_m_freeze and n_m_thaw on closed db 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:05Z urn:sha1:9244f588608ccedeab5e82e965a86c04a22be4b7 Neither of these accesses the database, so should be safe. Add the tests to catch any changes in exception throwing. lib: handle xapian exception in n_m_remove_all_tags 2020-07-20T11:54:42Z David Bremner david@tethera.net 2020-07-09T00:17:04Z urn:sha1:a2b90dc084c0224e56c1e63773048545788c7ad4 At least the exception we already catch should be reported properly.