notmuch/performance-test/M00-new.sh

#!/usr/bin/env bash

test_description='notmuch new'

. $(dirname "$0")/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-tests: #!/bin/bash -> #!/usr/bin/env bash I couldn't run the performance tests on my machines due to a hardcoded bash path. Use env for finding bash in weird systems like NixOS. Signed-off-by: William Casarin <jb55@jb55.com> 2019-05-31 20:32:50 +02:00			`#!/usr/bin/env bash`
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 13:33:17 +01:00
			`test_description='notmuch new'`

perf-test: use $(dirname "$0") for sourcing perf-test-lib.sh Don't assume the tests are always run from within the source tree. 2017-09-25 22:38:20 +02:00			`. $(dirname "$0")/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 13:33:17 +01: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`