| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
There is only one set of tags, independant of the size of message
corpus chosen.
|
|
|
|
|
| |
The caching and uncaching seem to be necessarily manual, as timing the
initial notmuch new is one of our goals with this suite.
|
|
|
|
|
| |
Unpacking is not really the expensive step (compared to the initial
notmuch new), but this is a pre-requisite to caching the database.
|
|
|
|
|
| |
Output from tests is indented slightly in the same style as the
correctness tests.
|
|
|
|
|
|
|
|
|
| |
Austin suggested a while ago that the corpus size be printed in the
header. In the end it seems the corpus will be fixed per test script,
so this suggestion indeed makes sense.
The tabbing was wrapping on my usual 80 column terminal, so I joined
the input and output columns together.
|
|
|
|
|
| |
This patch just sets (non-exported) variables. The variable $debug is
already used, and $corpus_size will be used in following commits.
|
|
|
|
|
|
| |
Unlike in the correctness tests, the most common cause of non-zero
return seems to be the user interrupting, so killing the run seems
like the friendly thing to do.
|
|
|
|
|
| |
Austin Read enough Fine Manuals to figure out this is in multiples of
512 bytes.
|
|
This is not near as fancy as as the unit tests, on the theory that
the code should typically be crashing when performance tuning.
Nonetheless, there is plenty of room for improvement. Several more of
the pieces of the test infrastructure (e.g. the option parsing) could
be factored out into test/test-lib-common.sh
|