unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 30745@debbugs.gnu.org, Phillip Lord <phillip.lord@russet.org.uk>,
	Noam Postavsky <npostavs@gmail.com>,
	24402@debbugs.gnu.org
Subject: bug#30745: 26.0.91; ert should macros nest strangely
Date: Thu, 22 Jul 2021 15:13:29 +0200	[thread overview]
Message-ID: <874kcmjxty.fsf@gnus.org> (raw)
In-Reply-To: <CAArVCkT5UGeX8DkH+QXTk0dh2yh-SWwfx5it0351gkBT3MPLvQ@mail.gmail.com> (Philipp Stephani's message of "Sun, 29 Nov 2020 11:35:43 +0100")

Philipp Stephani <p.stephani2@gmail.com> writes:

> How many tests (besides the jsonrpc one) do we expect to be broken due
> to this? It seems that tests relying on such a bug are inherently
> brittle, so maybe we can bite the bullet and apply the patch
> nevertheless? Or introduce another hack in process.c that treats ERT
> tests specially, as if debug-on-error were bound?

I wanted to try Noam's patch set, but it's two years old, so it doesn't
apply any more.  Noam, do you have an updated patch set, by any chance?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-07-22 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 21:34 bug#30745: 26.0.91; ert should macros nest strangely Phillip Lord
2018-03-07 22:24 ` Phillip Lord
2018-03-08 14:49   ` bug#24402: " Phillip Lord
2018-03-08  0:12 ` Noam Postavsky
2018-03-08  8:54   ` Phillip Lord
2018-08-15  0:47     ` Noam Postavsky
2019-06-24 18:54       ` Lars Ingebrigtsen
2019-06-24 22:53         ` Noam Postavsky
2019-06-28  3:06           ` Noam Postavsky
2020-11-29 10:35           ` Philipp Stephani
2021-07-22 13:13             ` Lars Ingebrigtsen [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://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=874kcmjxty.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=24402@debbugs.gnu.org \
    --cc=30745@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=p.stephani2@gmail.com \
    --cc=phillip.lord@russet.org.uk \
    /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).