From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: noloader@gmail.com, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: make check fails due to missing test directory
Date: Sat, 4 May 2019 08:56:19 -0700 [thread overview]
Message-ID: <ff1f4ea2-b21d-19c6-bfba-237c406fdd2b@cs.ucla.edu> (raw)
In-Reply-To: <20190504092406.GA4139@ACM>
Alan Mackenzie wrote:
> The tests in make check are development tests. They're not build tests.
> In fact, they're fairly useless for anybody who isn't developing Emacs.
> Somebody who is developing Emacs will have the git repository.
In what sense does Emacs differ from other GNU packages, like Coreutils?
Coreutils has a series of tests that are similarly "useless" for anybody who
isn't developing Coreutils. However, builders of Coreutils can run 'make check'
to run these tests. If tests fail, builders can decide themselves whether to
install the build, or to stick with an older version. And they can report
problems to developers, often problems that the developers themselves couldn't
easily find. The developers and builders can then collaborate to fix the
problem. Yes, the process can be a bit awkward, but it beats leaving the bugs
unfixed. And no part of this process requires builders to understand the code
well enough to fix it.
Why shouldn't Emacs do that too?
next prev parent reply other threads:[~2019-05-04 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 18:41 make check fails due to missing test directory Jeffrey Walton
2019-05-03 19:13 ` Eli Zaretskii
2019-05-03 22:01 ` Paul Eggert
2019-05-04 9:24 ` Alan Mackenzie
2019-05-04 15:56 ` Paul Eggert [this message]
2019-05-04 16:44 ` Michael Albinus
2019-05-16 17:54 ` Emacs distribution tarball now supports 'make check' Paul Eggert
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff1f4ea2-b21d-19c6-bfba-237c406fdd2b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=noloader@gmail.com \
/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://git.savannah.gnu.org/cgit/emacs.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).