unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
blob f546c07048cbf90c2fca197e77a80b2bf64c7ab5 4318 bytes (raw)
name: test/atomicity 	 # note: path name is non-authoritative(*)

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
 
#!/bin/bash
test_description='atomicity'
. ./test-lib.sh

# 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.

if test_expect_success "prereq: GDB is present" "which gdb"; then
    test_set_prereq GDB
fi

# Create a maildir structure to also stress flag synchronization
mkdir $MAIL_DIR/cur
mkdir $MAIL_DIR/new
mkdir $MAIL_DIR/tmp
mkdir $MAIL_DIR/.remove-dir

# 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

# 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
increment_mtime $MAIL_DIR/cur
increment_mtime $MAIL_DIR/new
increment_mtime $MAIL_DIR

# Prepare a snapshot of the updated maildir.  The gdb script will
# update the database in this snapshot as it goes.
cp -ra $MAIL_DIR $MAIL_DIR.snap
cp ${NOTMUCH_CONFIG} ${NOTMUCH_CONFIG}.snap
NOTMUCH_CONFIG=${NOTMUCH_CONFIG}.snap notmuch config set database.path $MAIL_DIR.snap


test_begin_subtest '"notmuch new" is idempotent under arbitrary aborts'

# 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
gdb -tty /dev/null -batch -x $TEST_DIRECTORY/atomicity.gdb notmuch >/dev/null 2>/dev/null

# Get the final, golden output
notmuch search '*' > expected

# 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

        i=$(expr $end - 1)
    fi
done
test_expect_equal GDB "$(cat searchall)" "$(cat expectall)"

test_expect_success GDB "detected $outcount>10 abort points" "test $outcount -gt 10"

test_done

debug log:

solving f546c07 ...
found f546c07 in https://yhetil.org/notmuch/1307822683-848-17-git-send-email-amdragon@mit.edu/
found 817819a in https://yhetil.org/notmuch/1307822683-848-5-git-send-email-amdragon@mit.edu/

applying [1/2] https://yhetil.org/notmuch/1307822683-848-5-git-send-email-amdragon@mit.edu/
diff --git a/test/atomicity b/test/atomicity
new file mode 100755
index 0000000..817819a


applying [2/2] https://yhetil.org/notmuch/1307822683-848-17-git-send-email-amdragon@mit.edu/
diff --git a/test/atomicity b/test/atomicity
index 817819a..f546c07 100755

Checking patch test/atomicity...
Applied patch test/atomicity cleanly.
Checking patch test/atomicity...
Applied patch test/atomicity cleanly.

index at:
100755 f546c07048cbf90c2fca197e77a80b2bf64c7ab5	test/atomicity

(*) Git path names are given by the tree(s) the blob belongs to.
    Blobs themselves have no identifier aside from the hash of its contents.^

Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).