thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.22 2015-08-07T19:56:39Z 2015-08-07T19:56:39Z Tomi Ollila tomi.ollila@iki.fi 2015-08-06T09:13:36Z urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741 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. 2015-05-31T17:14:42Z J. Lewis Muir jlmuir@imca-cat.org 2015-05-27T17:53:52Z urn:sha1:d08af93c65310c2d5ec8033040854f8ff4e5550f The word "setup" is a noun, not a verb. Change occurrences of "setup" where used as a verb to "set up". 2014-03-15T00:47:43Z David Bremner david@tethera.net 2014-03-07T12:03:23Z urn:sha1:8fcc3260a9a936de72d755e61d93d5a24380e8b7 It seems that between version 1.26 and 1.27 of gnu tar, directories to be extracted read with --files-from are no longer recursively extacted. This patch puts them on the command line instead. 2013-12-09T20:00:38Z David Bremner david@tethera.net 2013-12-01T03:00:03Z urn:sha1:2de8ce9b37bfaed7c5a962a5316dbc9c9c3cb2c8 The new revision of the performance test includes manifests for each corpus, so update the support library to use these manifests at the same time. 2012-12-31T01:12:11Z David Bremner bremner@debian.org 2012-12-26T16:29:45Z urn:sha1:8d05dcfffe001dc64d750f509e049340320b4dd9 As with the valgrind logs, we print a (very) brief summary and leave the log for inspection. 2012-12-25T12:49:24Z David Bremner bremner@debian.org 2012-12-16T12:33:17Z urn:sha1:098ef4af4d0a52a6b4daed5324a7c77f6c9108da The idea is run some code under valgrind --leak-check=full and report a summary, leaving the user to peruse the log file if they want. We go to some lengths to preserve the log files from accidental overwriting; the full corpus takes about 3 hours to run under valgrind on my machine. The naming of the log directories may be slightly controversial; in the unlikely event of two runs in less than a second, the log will be overwritten. A previous version with mktemp+timestamp was dismissed as overkill; just mktemp alone does not sort nicely. One new test is included, to check notmuch new for memory leaks. 2012-12-15T12:17:58Z David Bremner bremner@debian.org 2012-12-04T02:59:56Z urn:sha1:5c35791d7cf7279024befc98e9d973af461336a3 There is only one set of tags, independant of the size of message corpus chosen. 2012-12-15T12:17:58Z David Bremner bremner@debian.org 2012-12-03T12:48:53Z urn:sha1:ceaf5ca6c02e494eee5b9b9aa955459b3cd29471 The caching and uncaching seem to be necessarily manual, as timing the initial notmuch new is one of our goals with this suite. 2012-12-15T12:17:57Z David Bremner bremner@debian.org 2012-12-03T12:13:31Z urn:sha1:74a883562b3e4593c75fa7625ff5cabab46a6466 Unpacking is not really the expensive step (compared to the initial notmuch new), but this is a pre-requisite to caching the database. 2012-12-15T12:17:57Z David Bremner bremner@debian.org 2012-12-06T01:41:44Z urn:sha1:925ebd1fde59b003a7215e8cd7e07225a8f8915d Output from tests is indented slightly in the same style as the correctness tests.