notmuch/test/T050-new.sh, branch 0.28thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.282018-05-26T23:46:44Ztest: fix hardcoded paths in T050-new.sh2018-05-26T23:46:44ZDavid Bremnerdavid@tethera.net2018-05-26T23:46:44Zurn:sha1:46cf1a98f3616f1a503f7b04c0f6980930aedaf2
The previous paths will fail almost everywhere.
test: use --full-scan in T050-new.sh2018-05-22T16:29:59ZDavid Bremnerdavid@tethera.net2018-04-29T23:19:42Zurn:sha1:84b29637261adc3c647e078ad320258b371bd36b
Wherever the test relies on directories being scanned, this option
should be used to avoid skipping them due to mtimes on directories
matching the database.
test: add tests for notmuch new --full-scan2018-05-22T16:29:48ZDavid Bremnerdavid@tethera.net2018-04-29T23:19:41Zurn:sha1:d1acff615306a732054b3cc2bec502a419ed861a
Most of these just check that adding the flag does not break existing
functionality. The one test that does check the full-scan
functionality had to be rewritten to output debugging info.
lib: choose oldest message when breaking reference loops2018-04-24T02:00:20ZDavid Bremnerdavid@tethera.net2018-04-20T14:59:48Zurn:sha1:491b1f4b4082bee18418942846ec6508856be7b4
This preserves a sensible thread order
test: add known broken test for thread ordering from a loop2018-04-24T02:00:20ZDavid Bremnerdavid@tethera.net2018-04-14T01:46:09Zurn:sha1:4e085b6d92909b8f6d4a4b18ccd97fac8b7df620
The previous loop handling code chooses the last message in the
message list, which turns out to be the last in date order.
See the comment in _notmuch_thread_create.
lib: break reference loop by choosing arbitrary top level msg2018-04-20T14:23:31ZDavid Bremnerdavid@tethera.net2018-04-14T01:08:05Zurn:sha1:9293d6da27494d7b607c945c6678bc890749b94f
Other parts of notmuch (e.g. notmuch show) expect each thread to
contain at least one top level message, and crash if this expectation
is not met.
test: add known broken test for indexing an In-Reply-To loop.2018-04-20T14:23:31ZDavid Bremnerdavid@tethera.net2018-03-20T21:22:35Zurn:sha1:ab55ca8e0a84b8e00e42860fa0025c1ae86b4478
This documents the bug discussed in
id:87d10042pu.fsf@curie.anarc.at
test: test regexp based new.ignore2017-12-15T11:55:02ZJani Nikulajani@nikula.org2017-10-14T13:16:28Zurn:sha1:7354d6d8f6fe413097e4fe3dc450594f016334a9
Just some basics.
test: use $(dirname "$0") for sourcing test-lib.sh2017-10-20T22:52:49ZJani Nikulajani@nikula.org2017-09-25T20:38:19Zurn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa
Don't assume the tests are always run from within the source tree.
test: Fix T050-new.sh on some Travis CI machines2017-08-30T10:24:44ZVladimir Panteleevnotmuch@thecybershadow.net2017-08-17T17:51:42Zurn:sha1:95b82bb326eccbc9a1e683b5764b93795b166ca2
On some system configurations, setting a breakpoint on the "add_file"
function then issuing "continue" in gdb causes the debugger to
seemingly jump over the add_file invocation. This results in a test
failure, as the "Handle files vanishing between scandir and add_file"
subtest expects add_file to be called and fail due to the vanishing
file. The compiler optimization level also plays a role - the problem
can be reproduced with CFLAGS having -O2 but not -Og.
This problem was observed manifesting as a test failure on Travis CI
configured with "dist: trusty" and "sudo: false". It was not
reproducible on a local Docker image of Travis' runtime environment,
so Travis' virtualization infrastructure likely plays a role as well.
* T050-new.sh: Breakpoint notmuch_database_add_message instead of
add_file to the same effect, and avoid bad gdb behaviour on Travis
CI.
Amended by db:
s/notmuch_database_add_message/notmuch_database_index_file/
Somehow the wrapper function doesn't work as a breakpoint; perhaps due
to inlining.