From: Tino Calancha <tino.calancha@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 26337@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#26337: 26.0.50; Command to run tests with latest source
Date: Mon, 3 Apr 2017 12:41:00 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704031217500.2091@calancha-pc> (raw)
In-Reply-To: <sud1cug77r.fsf@fencepost.gnu.org>
On Sun, 2 Apr 2017, Glenn Morris wrote:
> Tino Calancha wrote:
>
>> I often while debugging follow this workflow:
>>
>> 1) Make some changes in one branch.
>> 2) Compile Emacs.
>> 3) Run one test file with:
>> M-& emacs -batch -l ert -l ? -f ert-run-tests-batch-and-exit RET
> The test file names are completable using whatever your shell uses for
> file name completion (eg alt-/ in bash). In emacs-25 they are completable
> with bash TAB completion (from bash Makefile completion), which was nicer.
>
> So personally I'm not sure I see the need to add an autoloaded ert
> command to do this.
The autocomplete is not the main point of this addition. The point is
let you run a test file (not necessarily from the official test suite),
in batch using the latest compiled source with easy.
> I use make for step 3. It seems natural after using it in step 2. Eg
>
> cd test
> make lisp/vc/ediff-ptch-tests.log
>
> (till yesterday, it used to work without ".log" as well - see emacs-devel)
You are right, that sounds pretty good. Note, it doesn't work if the test
you want to run it doesn't exit in the current branch or it's not as you
expect..
I use to write the test file in /tmp. Then i can run the test after
compile the sources for whatever branch.
For example, last week i copied
test/lisp/emacs-lisp/cl-lib-tests.el
from commit 1f5b4ed628
into /tmp. Then, i checkout several earlier commits to see when
cl-lib-symbol-macrolet test fail. It started failing with 0d112c00ba,
but in that commit all tests in
/lisp/emacs-lisp/cl-lib-tests.el pass because
'cl-lib-symbol-macrolet' test was added later. In that branch i must run
the file copied in /tmp. In that case is handy to use the porposed
command.
You can think of it as a manual bisect, but it's not exactly that.
Suppose now you are in a branch fixing this issue. You change things,
compile and then you run the test in /tmp, which contains the
'cl-lib-symbol-macrolet' test.
next prev parent reply other threads:[~2017-04-03 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 5:28 bug#26337: 26.0.50; Command to run tests with latest source Tino Calancha
2017-04-02 15:27 ` Glenn Morris
2017-04-03 3:41 ` Tino Calancha [this message]
2017-04-03 23:40 ` Glenn Morris
2017-04-04 0:33 ` Tino Calancha
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1704031217500.2091@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=26337@debbugs.gnu.org \
--cc=rgm@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.