notmuch/test/atomicity, branch 0.10.1 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.10.1 2011-11-14T21:08:53Z test/atomicity: change shebang to '#!/usr/bin/env bash' 2011-11-14T21:08:53Z Tomi Ollila tomi.ollila@iki.fi 2011-11-13T08:52:35Z urn:sha1:9cda22c39b3ec33db09d4f5df5f59c7042658991 test/atomicity: redirect output from "which" 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. test: make atomicity setup conditional on gdb being 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. new: Wrap adding and removing messages in atomic sections. 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. test: use test_expect_equal_file in atomicity 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. test: Convert atomicity test to use test_subtest_known_broken 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. test: Test atomicity of notmuch new. 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.