From: Ethan Glasser-Camp <glasse@cs.rpi.edu>
To: notmuch@notmuchmail.org
Cc: Ethan Glasser-Camp <ethan@betacantrips.com>
Subject: [PATCH] Document the dependency on dtach in the test suite
Date: Mon, 16 Jan 2012 12:16:08 -0500 [thread overview]
Message-ID: <1326734168-21064-1-git-send-email-glasse@cs.rpi.edu> (raw)
From: Ethan Glasser-Camp <ethan@betacantrips.com>
dtach (and before that, screen) are used to run emacs with more
verisimilitude, but this is only mentioned in the NEWS. Mention this
in the test/README file, to make it easier to find out why a bunch of
tests are failing/skipped.
Signed-off-by: Ethan Glasser-Camp <ethan@betacantrips.com>
---
Just cutting my teeth on the codebase, and it took me a little while
to figure this out, so I thought I'd document it.
test/README | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/test/README b/test/README
index bde6db0..29afb3b 100644
--- a/test/README
+++ b/test/README
@@ -6,6 +6,11 @@ When fixing bugs or enhancing notmuch, you are strongly encouraged to
add tests in this directory to cover what you are trying to fix or
enhance.
+Prerequisites
+-------------
+emacs is run within dtach, so you need to have that installed to run
+emacs tests (or crypto tests, which rely on emacs to run).
+
Running Tests
-------------
The easiest way to run tests is to say "make test", (or simply run the
--
1.7.5.4
next reply other threads:[~2012-01-16 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 17:16 Ethan Glasser-Camp [this message]
2012-01-16 17:55 ` [PATCH] Document the dependency on dtach in the test suite Dmitry Kurochkin
2012-01-18 12:19 ` [PATCH] test: always report missing prereqs, independent of `--verbose' option Pieter Praet
2012-01-18 13:53 ` Tomi Ollila
2012-01-20 0:24 ` Pieter Praet
2012-01-20 0:33 ` Pieter Praet
2012-02-21 3:27 ` 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=1326734168-21064-1-git-send-email-glasse@cs.rpi.edu \
--to=glasse@cs.rpi.edu \
--cc=ethan@betacantrips.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).