From: David Bremner <david@tethera.net>
To: Milton Vandersloot <miltonrobertvandersloot1412@protonmail.com>,
"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Mark Emacs as prerequisite for tests which require it
Date: Mon, 02 Aug 2021 15:02:06 -0300 [thread overview]
Message-ID: <87czqvzpwh.fsf@tethera.net> (raw)
In-Reply-To: <NL_Di4YUqTedH1QQtFWnG4M2ZSV3qrZVDPRe1GgRDzMA6q0K1iAYO0plk_b-2KNREfkTS4jrBXlrAQGxz7ZP-il0Ojn966hScXRrLEKf3-c=@protonmail.com>
Milton Vandersloot <miltonrobertvandersloot1412@protonmail.com> writes:
> Dear notmuch developers
>
> The notmuch test suite depends on some external dependencies to finish successfully (i.e. no failures but maybe some skips), one of them being Emacs.
> As I had no Emacs installed, I discovered that some tests fail and do not state properly that Emacs is needed for them.
> Below are small sed commands (was easier this way) which put the "test_require_external_prereq emacs" to the missing places.
>
> For some tests (those which test Emacs capabilities) it is clear that Emacs is a necessity, some tests in particular the crypto tests (T350, T355, T357) do require Emacs only for generating a initial mail to index/test on. Here it would in my opinion be better to find an alternative way of producing that e-mail so these tests can be run without Emacs (That would reduce the long list of test names below tremendously). A promising approach would be using the same idea as the last tests in T357-index-decryption.sh, they use "add_email_corpus crypto" for (what seems to me) populating the mail archive.
I think this is now handled by the commits following cd9ec20a49, which
will be in the next release of notmuch.
prev parent reply other threads:[~2021-08-02 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 8:37 Mark Emacs as prerequisite for tests which require it Milton Vandersloot
2021-08-02 18:02 ` David Bremner [this message]
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=87czqvzpwh.fsf@tethera.net \
--to=david@tethera.net \
--cc=miltonrobertvandersloot1412@protonmail.com \
--cc=notmuch@notmuchmail.org \
/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).