thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.31 2017-12-05T01:04:38Z 2017-12-05T01:04:38Z David Bremner david@tethera.net 2017-12-02T12:53:04Z urn:sha1:1e4e8e3bf564ea190b42e9347b22c62fa6b78396 In 8e7fb88237aedea22 Jani replaced the use of $(pwd -P) to find the TEST_DIRECTORY in order to better support out of tree builds. Unfortunately the performance-tests need a different value for the variable and were thus broken. This commit splits out the setting of this variable for the two sets of tests. Performance tests still don't work out of tree, because the handling of the downloaded corpus needs to be updated. 2017-10-20T22:54:22Z Jani Nikula jani@nikula.org 2017-09-25T20:38:24Z urn:sha1:2e16b051528b273e16306224f128b28d0091bc6a Make a distinction between source and build directories. 2017-03-18T16:34:32Z David Bremner david@tethera.net 2017-03-18T16:34:32Z urn:sha1:0c8ce66ef4645e84887884fb5669fe158172f426 This allows the use of redirection in the tests 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.