notmuch/test/T240-dump-restore.sh, branch 0.25thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.252017-04-06T17:37:02Ztest: standardize argument order to test_expect_equal_file2017-04-06T17:37:02ZDavid Bremnerdavid@tethera.net2017-04-05T00:36:29Zurn:sha1:ec3937b5cd2884504d5536dc8631a15fd506050b
It is annoying to debug failing tests when the interpretation of the
diffs is reversed for some tests.
Merge branch 'release'2017-04-01T12:36:34ZDavid Bremnerdavid@tethera.net2017-04-01T12:36:34Zurn:sha1:33e58021958f8069ad46d7bd05cf586676fb6ae7
Final 0.24.1 release
cli/dump: bump dump format version to 32017-04-01T12:10:15ZDavid Bremnerdavid@tethera.net2017-03-31T10:55:17Zurn:sha1:d47e18411807b57cac9aaa29a7435a9f83720b81
No changes to the format of the body, but the header format was
fixed, and version 2 headers probably shouldn't be relied on.
cli/dump: fix bug in dump header2017-04-01T12:09:33ZDavid Bremnerdavid@tethera.net2017-03-28T11:09:03Zurn:sha1:1f3c7916f82774cacbfbb0fbc9d0e0aaae9399b3
Fix copy paste error.
test: add known broken test for dump header2017-04-01T12:09:20ZDavid Bremnerdavid@tethera.net2017-03-28T11:09:02Zurn:sha1:704bd3d8a249b4041aa6a4204032f2b336f374e8
Apparently nobody uses the list of "what was included in the dump"
test: add known broken test for dump header2017-04-01T00:18:54ZDavid Bremnerdavid@tethera.net2017-03-28T11:09:02Zurn:sha1:c0a3bd956af91d08d95a993f4fd971a617a5517b
Apparently nobody uses the list of "what was included in the dump"
test: require test_begin_subtest before test_expect_success2017-03-09T13:01:21ZJani Nikulajani@nikula.org2017-02-26T13:43:00Zurn:sha1:d0cd253b37646d9364d046e1d3edb022a58c105a
Unify the subtests by requiring test_begin_subtest before
test_expect_success. (Similar change for test_expect_code will
follow.)
This increases clarity in the test scripts by having a separate line
for the start of the subtest with the heading, and makes it possible
to simplify the test infrastructure by making all subtests similar.
test: don't use dump and restore in a pipeline2016-06-29T07:03:14ZDavid Bremnerdavid@tethera.net2016-06-28T08:24:07Zurn:sha1:496dccf44fadf4c8ee190e98d3cba54a8e828f97
This has been wrong since bbbdf0478ea, but the race condition was not
previously been (often?) triggered in the tests. With the DB_RETRY_LOCK
patches, it manifests itself as a deadlock.
CLI: add optional config data to dump output.2016-05-25T10:07:56ZDavid Bremnerdavid@tethera.net2016-03-22T10:54:50Zurn:sha1:e042a25a3fd8706b6e1ee7bdf527bb17ecb74c6a
Note that it changes the default dump output format, but doesn't break
existing notmuch-restore. It might break user scripts though.
test: make script exit (1) if it "fails" to source (.) a file2015-08-07T19:56:39ZTomi Ollilatomi.ollila@iki.fi2015-08-06T09:13:36Zurn: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.