debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-11-22 10:58:10 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
notmuch/test/T380-atomicity.sh

101 lines
4.2 KiB
Bash
Raw Normal View History

test/atomicity: change shebang to '#!/usr/bin/env bash'
2011-11-13 09:52:35 +01:00
#!/usr/bin/env bash
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test_description='atomicity'
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 11:13:36 +02:00
. ./test-lib.sh || exit 1
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
# This script tests the effects of killing and restarting "notmuch
# new" at arbitrary points. If notmuch new is properly atomic, the
# final database contents should be the same regardless of when (or
# if) it is killed and restarted.
test: cleanup gdb external dependency in atomicity tests Change atomicity tests to use the new external binary dependencies. This simplifies the code and makes output consistent.
2011-12-01 23:02:46 +01:00
if test_require_external_prereq gdb; then
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
# Create a maildir structure to also stress flag synchronization
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
mkdir $MAIL_DIR/cur
mkdir $MAIL_DIR/new
mkdir $MAIL_DIR/tmp
mkdir $MAIL_DIR/.remove-dir
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Prepare the initial database
generate_message [subject]='Duplicate' [filename]='duplicate:2,' [dir]=cur
generate_message [subject]='Remove' [filename]='remove:2,' [dir]=cur
generate_message [subject]='"Remove duplicate"' [filename]='remove-duplicate:2,' [dir]=cur
cp $MAIL_DIR/cur/remove-duplicate:2, $MAIL_DIR/cur/remove-duplicate-copy:2,
generate_message [subject]='Rename' [filename]='rename:2,' [dir]=cur
generate_message [subject]='"Rename duplicate"' [filename]='rename-duplicate:2,' [dir]=cur
generate_message [subject]='"Move 1"' [filename]='move1:2,' [dir]=cur
generate_message [subject]='"Move 2"' [filename]='move2:2,' [dir]=new
generate_message [subject]='Flag' [filename]='flag:2,' [dir]=cur
generate_message [subject]='"Flag duplicate"' [filename]='flag-duplicate:2,' [dir]=cur
cp $MAIL_DIR/cur/flag-duplicate:2, $MAIL_DIR/cur/flag-duplicate-copy:2,F
generate_message [subject]='"Remove directory"' [filename]='remove-directory:2,' [dir]=.remove-dir
generate_message [subject]='"Remove directory duplicate"' [filename]='remove-directory-duplicate:2,' [dir]=.remove-dir
cp $MAIL_DIR/.remove-dir/remove-directory-duplicate:2, $MAIL_DIR/cur/
notmuch new > /dev/null
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Make all maildir changes, but *don't* update the database
generate_message [subject]='Added' [filename]='added:2,' [dir]=cur
cp $MAIL_DIR/cur/duplicate:2, $MAIL_DIR/cur/duplicate-copy:2,
generate_message [subject]='"Add duplicate"' [filename]='add-duplicate:2,' [dir]=cur
generate_message [subject]='"Add duplicate copy"' [filename]='add-duplicate-copy:2,' [dir]=cur
rm $MAIL_DIR/cur/remove:2,
rm $MAIL_DIR/cur/remove-duplicate-copy:2,
mv $MAIL_DIR/cur/rename:2, $MAIL_DIR/cur/renamed:2,
mv $MAIL_DIR/cur/rename-duplicate:2, $MAIL_DIR/cur/renamed-duplicate:2,
mv $MAIL_DIR/cur/move1:2, $MAIL_DIR/new/move1:2,
mv $MAIL_DIR/new/move2:2, $MAIL_DIR/cur/move2:2,
mv $MAIL_DIR/cur/flag:2, $MAIL_DIR/cur/flag:2,F
rm $MAIL_DIR/cur/flag-duplicate-copy:2,F
rm $MAIL_DIR/.remove-dir/remove-directory:2,
rm $MAIL_DIR/.remove-dir/remove-directory-duplicate:2,
rmdir $MAIL_DIR/.remove-dir
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Prepare a snapshot of the updated maildir. The gdb script will
# update the database in this snapshot as it goes.
test/atomicity: use a more portable 'cp' form -a already implies -r/-R, so no need for both. FreeBSD's cp complains: cp: the -R and -r options may not be specified together
2012-05-30 09:02:03 +02:00
cp -a $MAIL_DIR $MAIL_DIR.snap
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
cp ${NOTMUCH_CONFIG} ${NOTMUCH_CONFIG}.snap
NOTMUCH_CONFIG=${NOTMUCH_CONFIG}.snap notmuch config set database.path $MAIL_DIR.snap
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Execute notmuch new and, at every call to rename, snapshot the
# database, run notmuch new again on the snapshot, and capture the
# results of search.
#
# -tty /dev/null works around a conflict between the 'timeout' wrapper
# and gdb's attempt to control the TTY.
export MAIL_DIR
test: Port atomicity test to Python Previously, this was implemented using a horrible GDB script (because there is no such thing as a non-horrible GDB script). This GDB script often broke with newer versions of GDB for mysterious reasons. Port the test script to GDB's Python API, which makes the code much cleaner and, hopefully, more stable.
2014-10-03 18:58:03 +02:00
gdb -tty /dev/null -batch -x $TEST_DIRECTORY/atomicity.py notmuch 1>gdb.out 2>&1
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Get the final, golden output
notmuch search '*' > expected
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
# Check output against golden output
outcount=$(cat outcount)
echo -n > searchall
echo -n > expectall
for ((i = 0; i < $outcount; i++)); do
if ! cmp -s search.$i expected; then
# Find the range of interruptions that match this output
for ((end = $i + 1 ; end < $outcount; end++)); do
if ! cmp -s search.$i search.$end; then
break
fi
done
echo "When interrupted after $test/backtrace.$(expr $i - 1) (abort points $i-$(expr $end - 1))" >> searchall
cat search.$i >> searchall
cat expected >> expectall
echo >> searchall
echo >> expectall
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: make atomicity setup conditional on gdb being present. The setup is useless if gdb is not present, so it doesn't hurt to skip it. The diff here is huge, but the commit is really just moving most of the script inside the initial if, and adding an else block to print a warning.
2011-09-25 03:45:33 +02:00
i=$(expr $end - 1)
fi
done
test: cleanup gdb external dependency in atomicity tests Change atomicity tests to use the new external binary dependencies. This simplifies the code and makes output consistent.
2011-12-01 23:02:46 +01:00
fi
test: Convert atomicity test to use test_subtest_known_broken This is required because test_expect_equal_failure went away.
2011-09-11 00:02:34 +02:00
test_begin_subtest '"notmuch new" is idempotent under arbitrary aborts'
test: cleanup gdb external dependency in atomicity tests Change atomicity tests to use the new external binary dependencies. This simplifies the code and makes output consistent.
2011-12-01 23:02:46 +01:00
test_expect_equal_file searchall expectall
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test: cleanup gdb external dependency in atomicity tests Change atomicity tests to use the new external binary dependencies. This simplifies the code and makes output consistent.
2011-12-01 23:02:46 +01:00
test_expect_success "detected $outcount>10 abort points" "test $outcount -gt 10"
test: Test atomicity of notmuch new. This tests notmuch new's ability to recover from arbitrary stopping failures. It interrupts notmuch new after every database commit and, on every resulting database snapshot, re-runs notmuch new to completion and checks that the final database state is invariant.
2011-01-28 19:03:24 +01:00
test_done
Reference in a new issue Copy permalink