From: akater <nuclearspace@gmail.com>
To: 51409@debbugs.gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#51409: 29.0.50; Basic erts functionality seems to be broken
Date: Tue, 26 Oct 2021 11:09:58 +0000 [thread overview]
Message-ID: <87h7d4dou1.fsf@gmail.com> (raw)
I can't make some basic erts tests work; this looks like an erts bug.
In the following file, the specified result of the first test is what
you'd see in a emacs-lisp-mode buffer. When the test is run, you don't
get this result.
Furthermore, load the following file in emacs -Q and run
(ert-run-tests-interactively t). I observe, on the recent build from
master, that the /resulting/ after- string is different depending on
what the /specified/ after- string was, which certainly should not
happen.
This is true in two instances of Emacs built with vastly different
settings so I omitted Emacs build details.
;;; -*- lexical-binding: t; -*-
(require 'ert)
(require 'ert-x)
(with-current-buffer (find-file-noselect "/tmp/erts-tests.erts")
(erase-buffer)
(insert
"Name: erts-with-basic-newline
Code: (lambda () (emacs-lisp-mode) (newline nil t))
Point-Char: |
No-Before-Newline: t
No-After-Newline: t
=-=
(whatever|
=-=
(whatever
|
=-=-=
")
(save-buffer))
(ert-deftest my-erts-tests ()
(ert-test-erts-file (ert-resource-file "/tmp/erts-tests.erts")))
(with-current-buffer (find-file-noselect "/tmp/erts-tests-with-garbage.erts")
(erase-buffer)
(insert
"Name: erts-with-basic-newline-and-garbabe
Code: (lambda () (emacs-lisp-mode) (newline nil t))
Point-Char: |
No-Before-Newline: t
No-After-Newline: t
=-=
(whatever|
=-=
(whatever
should-not-be-here |
=-=-=
")
(save-buffer))
(ert-deftest my-erts-tests-with-garbage ()
(ert-test-erts-file (ert-resource-file "/tmp/erts-tests-with-garbage.erts")))
next reply other threads:[~2021-10-26 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 11:09 akater [this message]
2021-10-27 14:14 ` bug#51409: 29.0.50; Basic erts functionality seems to be broken Lars Ingebrigtsen
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=87h7d4dou1.fsf@gmail.com \
--to=nuclearspace@gmail.com \
--cc=51409@debbugs.gnu.org \
--cc=larsi@gnus.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.