thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.9_rc1 2011-09-25T12:12:48Z 2011-09-25T12:12:48Z David Bremner bremner@debian.org 2011-09-25T12:12:48Z urn:sha1:2697f623ae1534b669e182934ade124bd9cfd7ad Without redirection, this produced some slightly confusing output in case gdb was present. 2011-09-25T01:45:33Z David Bremner bremner@debian.org 2011-09-25T01:45:33Z urn:sha1:c468f3703efc869d62d976ba177e2d0afd7b08ad The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning. 2011-09-24T23:00:29Z Austin Clements amdragon@mit.edu 2011-01-29T16:25:56Z urn:sha1:bff30540d86c77aacbc2c133c83aa7ccee823b48 This addresses atomicity of tag synchronization, the last atomicity problems in notmuch new. Each message add or remove is wrapped in its own atomic section, so interrupting notmuch new doesn't lose progress. 2011-09-13T12:31:46Z David Bremner bremner@debian.org 2011-09-13T12:31:46Z urn:sha1:73ed66a501537fc145b6b6250513ec94c7b7e659 The documentation claims this is more robust, and it seems to work fine to switch to the _file variant. 2011-09-13T12:28:08Z David Bremner bremner@debian.org 2011-09-10T22:02:34Z urn:sha1:05a522c5fa00bd6e0dc15e8cb858cdc45db801bf This is required because test_expect_equal_failure went away. 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-01-28T18:03:24Z urn:sha1:9ade8160a6a3f6f55996d7a58dc2cd81a6df8395 This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant. 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-05-12T13:11:36Z urn:sha1:003e718020b335f329f852ff1a3da23873d2ff6e This makes test_expect_* return non-zero if the test fails, so the caller can make decisions based on this, such as setting test prerequisites. 2011-09-13T02:35:59Z Austin Clements amdragon@mit.edu 2011-05-12T13:09:06Z urn:sha1:5ae1b9c328518a3b09be827ee59498b0598119ff For these types of tests, the test name is previously recorded in a variable, not passed to the test function, so pass this variable to test_skip. 2011-09-13T02:35:21Z David Bremner bremner@debian.org 2011-09-13T01:40:57Z urn:sha1:22af786838793ed97fa3dbb1d223e90602912b71 This means that test_subtest_known_broken needs to be called before every known broken subtest, which is no different than what is documented for the test_begin_subtest case. The assumption is that every test ends up calling either skipping, calling test_ok_ or test_failure_ and and the latter in turn delegate to the known_broken versions in the case where test_subtest_known_broken_ is set. 2011-09-10T18:00:17Z David Bremner bremner@debian.org 2011-09-10T18:00:17Z urn:sha1:0a7aa617d59a1c40efb0fa7726fb74bded9e240b Using the new test_subtest_known_broken support thanks to Dmitry Kurochkin. This makes the output less scary until we can fix the underlying problems.