all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 51131@debbugs.gnu.org, Helmut Eller <eller.helmut@gmail.com>
Subject: bug#51131: 29.0.50; Segfault in ERT test
Date: Mon, 11 Oct 2021 14:56:48 +0200	[thread overview]
Message-ID: <871r4riusv.fsf@gnus.org> (raw)
In-Reply-To: <CAArVCkTGbYLth__M8zBG20EvjjLjJCFM80abU6AkXWF=bJh9MA@mail.gmail.com> (Philipp Stephani's message of "Mon, 11 Oct 2021 14:39:41 +0200")

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

> I don't think that's the right fix. I added backtrace support in batch
> mode primarily for unit tests running on CI systems; this is exactly
> the situation where I want backtrace-on-error-noninteractive to be t.
> Can we revert commit 07edc28bdbfeeaeb1008b4fe21bfda586feae562 and find
> a better way?

ert wants to collect the backtrace, but the test itself subverted that
(by setting debug-on-error to nil and then having an error in the test).

I don't see why Emacs should output a backtrace inside a test like that.

But Emacs will still output

Error running tests
  backtrace()
  #f(compiled-function () #<bytecode -0x1fecd686855e18f0>)()
  ert-run-tests-batch-and-exit()
  command-line-1(("-l" "/tmp/test.el" "-f" "ert-run-tests-batch-and-exit"))
  command-line()
  normal-top-level()

at the end.

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





      reply	other threads:[~2021-10-11 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  6:07 bug#51131: 29.0.50; Segfault in ERT test Helmut Eller
2021-10-11  9:14 ` Lars Ingebrigtsen
2021-10-11 12:39   ` Philipp Stephani
2021-10-11 12:56     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r4riusv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=51131@debbugs.gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=p.stephani2@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 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.