notmuch/performance-test/M00-new.sh

#!/bin/bash

test_description='notmuch new'

. ./perf-test-lib.sh || exit 1

# ensure initial 'notmuch new' is run by memory_start
uncache_database

memory_start

# run 'notmuch new' a second time, to test different code paths
memory_run "notmuch new" "notmuch new"

memory_done
perf-test: initial version of memory test infrastructure. 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-16 08:33:17 -04:00			`#!/bin/bash`

			`test_description='notmuch new'`

test: make script exit (1) if it "fails" to source (.) a file 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-08-06 12:13:36 +03:00			`. ./perf-test-lib.sh \|\| exit 1`
perf-test: initial version of memory test infrastructure. 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-16 08:33:17 -04:00
			`# ensure initial 'notmuch new' is run by memory_start`
			`uncache_database`

			`memory_start`

			`# run 'notmuch new' a second time, to test different code paths`
			`memory_run "notmuch new" "notmuch new"`

			`memory_done`