From: David Bremner <david@tethera.net>
To: Floris Bruynooghe <flub@devork.be>,
Tomi Ollila <tomi.ollila@iki.fi>,
notmuch@notmuchmail.org
Subject: Re: python CFFI bindings integration into notmuch build/test
Date: Sat, 16 Nov 2019 10:51:09 -0500 [thread overview]
Message-ID: <87eey7u8eq.fsf@tethera.net> (raw)
In-Reply-To: <878soiqclh.fsf@powell.devork.be>
Floris Bruynooghe <flub@devork.be> writes:
> Anyway, this looks good. Would you like some changes, e.g. the rename
> to notmuch2 or so as patches? What's the next step.
If you could look at the rename that would be great. Patches on top of
wip/cffi, or a ref for me to pull both sound fine.
> Kind of unrelated, but in my attempt to run the full notmuch test suite
> (cd tests; make test) I somehow ended up with lots of weird tags in my
> notmuch database and made the emacs UI pretty horrible - though it seems
> I haven't lost any email. I'm sure that was my fault somehow even
> though I was just trying to follow the readme. But if anyone has any
> hints how to recover from this that could save me some time :)
Hmm. I've never encountered that, but maybe it has to do with killing
the environment? The test harness uses the environment variable
NOTMUCH_CONFIG to point to a test database, and if that was deleted, it
would look in ~/.notmuch-config.
Still that would really only be tags from your pytest tests, and you'd
probably recognize those?
d
next prev parent reply other threads:[~2019-11-16 15:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:39 python CFFI bindings integration into notmuch build/test David Bremner
2019-11-04 1:39 ` [PATCH 1/5] bindings/python-cffi: preserve environment for tests David Bremner
2019-11-04 1:39 ` [PATCH 2/5] configure: check for python cffi module David Bremner
2019-11-04 21:24 ` Tomi Ollila
2019-11-04 1:39 ` [PATCH 3/5] build: optionally build python-cffi bindings David Bremner
2019-11-04 21:26 ` Tomi Ollila
2019-11-05 0:32 ` David Bremner
2020-05-22 1:06 ` Daniel Kahn Gillmor
2019-11-04 1:39 ` [PATCH 4/5] tests: run python-cffi tests David Bremner
2019-11-04 16:18 ` Tomi Ollila
2019-11-04 16:57 ` David Bremner
2019-11-04 21:45 ` Tomi Ollila
2019-11-04 22:04 ` Tomi Ollila
2019-11-06 2:19 ` David Bremner
2019-11-06 20:51 ` Tomi Ollila
2019-11-09 1:36 ` David Bremner
2019-11-09 21:59 ` Tomi Ollila
2019-11-22 3:03 ` David Bremner
2019-11-26 0:52 ` David Bremner
2019-12-03 12:16 ` David Bremner
2019-11-04 1:39 ` [PATCH 5/5] travis: add python3-{cffi,pytest,setuptools} David Bremner
2019-11-04 11:10 ` python CFFI bindings integration into notmuch build/test David Bremner
2019-11-05 20:47 ` Tomi Ollila
2019-11-06 2:22 ` David Bremner
2019-11-14 18:52 ` Floris Bruynooghe
2019-11-14 20:20 ` Tomi Ollila
2019-11-14 22:24 ` Floris Bruynooghe
2019-11-14 23:09 ` Floris Bruynooghe
2019-11-16 15:51 ` David Bremner [this message]
2019-11-17 14:40 ` Floris Bruynooghe
2019-11-17 16:09 ` David Bremner
2019-11-16 15:43 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eey7u8eq.fsf@tethera.net \
--to=david@tethera.net \
--cc=flub@devork.be \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).