GNU bug report logs - #50629
28.0.50; hard to debug an uncaught error with ert

Previous Next

Package: emacs;

Reported by: Mike Kupfer <mkupfer <at> alum.berkeley.edu>

Date: Thu, 16 Sep 2021 23:29:02 UTC

Severity: normal

Merged with 58941

Found in versions 28.0.50, 28.1.90

Full log

Message #16 received at 50629 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: 50629 <at> debbugs.gnu.org, Mike Kupfer <mkupfer <at> alum.berkeley.edu>
Subject: Re: bug#50629: 28.0.50; hard to debug an uncaught error with ert
Date: Sat, 27 Aug 2022 15:20:55 +0200

Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:

>> Anybody more familiar with ert.el know how this can be achieved?
>
> Not exactly this, I guess, but maybe as source of an idea?

[...]

> +                   (ert--pp-with-indentation-and-newline
> +                    (ert-test-result-with-condition-should-forms result))
>                     (ert--pp-with-indentation-and-newline
>                      (ert-test-result-with-condition-condition result)))
>                   (goto-char (1- (point-max)))
>
> leads to output
>
> Test f condition:
>     (((should
>        (equal 42
> 	      (foo)))
>       :form
>       (signal void-function
> 	      (bar))))
> (void-function bar)

Hm, yes...  But it'd be really useful to have the complete backtrace
instead of just the signal form, because the errors that this would be
most helpful for are often way down in the call stack.
This bug report was last modified 2 years and 228 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.