| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Conflicts resolved by inserting the 0.10.2 stanza before 0.11
|
| |
| |
| |
| |
| | |
Possibly this should be factored out into some kind of "run_python"
function.
|
| |
| |
| |
| |
| | |
This allows the debian-snapshot to continue working between when
debian/changelog is updated and when the release is tagged.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
We start modestly, with a (slightly modified) test case from Kazuo
Teramoto. Originally it just made sure the bindings didn't crash; here
we check that by comparing the output with that of notmuch search.
|
| |
| |
| |
| |
| | |
We want to make sure g_type_init is called before any GObject
functionality is used.
|
| |
| |
| |
| |
| |
| |
| | |
Since 2b0116119160f2dc83, Message.__str__ doesn't
construct a hash containing the thread data before
constructing the formatstring. This changes the formatstring
to accept positional parameters instead of a hash.
|
| |
| |
| |
| |
| | |
Now that licensing of notmuch-deliver has been harmonized with
notmuch, there is no reason not to export it.
|
| | |
|
| |
| |
| |
| |
| | |
maildrop-2.5.5 is GPL-3.
No change in functionality, just a precaution before relicensing.
|
| |
| |
| |
| |
| |
| |
| | |
The tar file of particular package (notmuch in this case) is named
as $(PACKAGE)-$(VERSION).tar.gz. Therefore the best way to remove
previous link to LATEST is to remove all files beginning with
LATEST-$(PACKAGE)- and not relying how $(VERSION) string is constructed.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The notmuchmail/releases page used to have LATEST-notmuch-<version>
to link to the latest notmuch source tarball. This is confusing on
web page and on disk when the file has been downloaded. This change
looks a bit inconsistent with the 'rm' command just executed before.
$(TAR_FILE) is defined (currently) as $(PACKAGE)-$(VERSION).tar.gz;
as long as the prefix stays $(PACKAGE)-$(VERSION) and version begins
with a digit then this line is good in execution point of view.
|
| |
| |
| |
| |
| | |
The goal here is to have a simple way of making sure all of the
binaries needed to run tests are available.
|
| |
| |
| |
| |
| |
| | |
This slipped in wrongly in commit 71e0082eff (due to my fault).
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now that types are checked correctly, we also need to make sure that all the
arguments actually are instances of these types. Otherwise the function calls
will fail and raise an exception similar to this one:
ctypes.ArgumentError: argument 3: <type 'exceptions.TypeError'>: expected
LP_LP_NotmuchMessageS instance instead of pointer to c_void_p
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
We were not returning anything at all, which does not match the API
documentation. Fixed. Thanks to Patrick Totzke for the heads up.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
| | |
|
| |
| |
| |
| |
| | |
no changes to the code, only makes compiling the docs smoother
as some rsT syntax errors were fixed
|
| |
| |
| |
| | |
no changes to the code, only fixed stuff denounced by `pep8 *py`
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add type information to the ctypes._FuncPtr wrappers and
use the wrapper classes instead of c_void_p for pointers
to notmuch_*_t.
This enables the ctypes library to type check parameters
being handed to functions from the notmuch library.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
| |
| |
| |
| | |
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
| |
| |
| |
| |
| |
| |
| | |
The fake missing binary functions check if the binary has already be
added to the diagnostic message to avoid duplicates. Unfortunately,
this check was buggy because the message string does not have the
trailing space.
|
| |
| |
| |
| |
| | |
The grep(1) command used in the fake binary functions was missing the
quiet option.
|
| | |
|
| |
| |
| |
| |
| |
| | |
test_missing_external_prereq_${binary}_ variable indicates that the
binary is missing. It must be set in test_declare_external_prereq()
outside of the fake $binary() function.
|
| |
| |
| |
| |
| |
| |
| | |
The process-lines function calls the notmuch binary. The location of
the binary may have been customized by the user, so it is better to
use the customized location rather than allowing the process-lines
function to search the user's PATH for the binary.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Asking xapian to sort the messages for us causes suboptimal IO patterns. This
would be useful, if we only wanted the first few results, but since we want
everything anyway, this is pessimization.
On 2011-10-29, a measurement on a 372981 messages instance showed that wall
time can be reduced from 28 minutes (sorted by Message-ID) to 15 minutes
(unsorted).
Timings on 189605 messages:
$ time notmuch.old dump
19.48user 5.83system 12:10.42elapsed 3%CPU (0avgtext+0avgdata 110656maxresident)k
3629584inputs+22720outputs (33major+7073minor)pagefaults 0swaps
$ echo 3 > /proc/sys/vm/drop_caches
$ time notmuch.new
14.89user 1.20system 3:23.58elapsed 7%CPU (0avgtext+0avgdata 46032maxresident)k
1256264inputs+22464outputs (43major+1990minor)pagefaults 0swaps
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This optimizes the user's tagging query to exclude messages that won't
be affected by the tagging operation, saving computation and IO for
redundant tagging operations.
For example,
notmuch tag +notmuch to:notmuch@notmuchmail.org
will now use the query
( to:notmuch@notmuchmail.org ) and (not tag:"notmuch")
In the past, we've often suggested that people do this exact
transformation by hand for slow tagging operations. This makes that
unnecessary.
|
| |
| |
| |
| |
| |
| | |
If emacs is not available, test_expect_equal would be called with only
one argument. The patch fixes this by quoting the (possibly empty)
$(cat OUTPUT) argument.
|
| |
| |
| |
| | |
Unfortunately, this is needed to avoid the emacs waiting loop.
|
| |
| |
| |
| | |
Useful when binary is called indirectly (e.g. from emacs).
|
| |
| |
| |
| | |
That are: dtach(1), emacs(1), emacsclient(1), gdb(1) and gpg(1).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some tests (e.g. crypto) do a common initialization required for all
subtests. The patch adds a check for missing external dependencies
during this initialization. If any prerequisites are missing, all
subtests are skipped.
The check is run on the first call of test_reset_state_ function, so
no changes for the tests are needed.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is existing support for general prerequisites in the test suite.
But it is not very convenient to use: every test case has to keep
track for it's dependencies and they have to be explicitly listed.
The patch aims to add better support for a particular type of external
dependencies: external executables. The main idea is to replace
missing external binaries with shell functions that have the same
name. These functions always fail and keep track of missing
dependencies for a subtest. The result reporting functions later can
check that an external binaries are missing and correctly report SKIP
result instead of FAIL. The primary benefit is that the test cases do
not need to declare their dependencies or be changed in any way.
|
| | |
|
| |
| |
| |
| |
| | |
Otherwise, we can set the EMACS_SERVER and return with an error. And
subsequent calls to test_emacs would assume that emacs server is running.
|
| |
| |
| |
| |
| | |
Currently, there is only one such variable test_subtest_known_broken_.
But more will be added in the future.
|
| |
| |
| |
| |
| |
| | |
If symbol-test is built in symbol-hiding with hardcoded g++ invokation,
it's not so easy to pass $(srcdir) which is required to find notmuch.h
when srcdir and builddir are separate directories.
|
|\| |
|
| |
| |
| |
| | |
Nothing fancy, but we can at least detect segmentation faults.
|
| |
| |
| |
| |
| | |
Explain the bug fix in slightly less technical language than in the
Debian changelog.
|
| | |
|