| Age | Commit message (Collapse) | Author |
|---|
|
We need to do it some day, and it is a bit annoying to read
deprecation messages in broken tests.
|
|
This removes some redudant includes, and will also make it easier to
introduce "#define _GNU_SOURCE", which must come before all system
includes.
|
|
The assignment of thread-ids is (apparently) non-deterministic in a
way that mostly seems to show up on multicore machines. In my tests
the number is different from that previously assumed by this test
about 15% of the time on a 50 thread (25 core) Xeon.
Since message id's are fixed, use a message known to be in the thread
of interest to pick out the correct thread-id.
|
|
Also test n_messages_destroy.
|
|
Check for (non)-crash.
|
|
Code is taken from the API docs, with the twist that the underlying
database is closed. Not crashing is the main point.
|
|
These are strictly to watch for crashes, so don't be too fussy about
the actual timestamps.
|
|
This is returning explicitely cached data, so no database access is needed.
|
|
This is similar to the case of toplevel messages. Currently everything
is cached, so no database access is necessary. This might change in
the future, but it should not crash in either case.
|
|
Include a test for the previously omitted non-trivial code path for
notmuch_thread_get_replies.
|
|
This is returning cached info, so does not need to access the (closed)
database.
|
|
This is just cached data, so as long as we don't prematurely free
anything, it should be fine.
|
