GNU bug report logs -
#24921
25.1; ERT fails to finish test run if test exceeeds max-lisp-eval-depth
Previous Next
Reported by: Gemini Lasswell <gazally <at> runbox.com>
Date: Thu, 10 Nov 2016 17:56:01 UTC
Severity: minor
Found in version 25.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24921 in the body.
You can then email your comments to 24921 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#24921
; Package
emacs
.
(Thu, 10 Nov 2016 17:56:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Gemini Lasswell <gazally <at> runbox.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 10 Nov 2016 17:56:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
If some code under test by ERT fails by recursing beyond
max-lisp-eval-depth, the resulting error stops the ERT test run without
marking the test as finished or failed.
To reproduce, using emacs -Q or not, enter this code into *scratch*:
(defun go-boom ()
(go-boom))
(ert-deftest test-go-boom ()
(should (go-boom)))
And then:
M-x eval-buffer RET
M-x ert RET RET
Result: The ERT window appears and shows that it is running the test.
But it never shows that it finishes. Any tests that you have defined
that follow test-go-boom in alphabetical order will not run. The echo
area will show the message "Lisp nesting exceeds ‘max-lisp-eval-depth’"
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#24921
; Package
emacs
.
(Sat, 27 Jul 2019 12:27:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 24921 <at> debbugs.gnu.org (full text, mbox):
Gemini Lasswell <gazally <at> runbox.com> writes:
> If some code under test by ERT fails by recursing beyond
> max-lisp-eval-depth, the resulting error stops the ERT test run without
> marking the test as finished or failed.
>
> To reproduce, using emacs -Q or not, enter this code into *scratch*:
>
> (defun go-boom ()
> (go-boom))
>
> (ert-deftest test-go-boom ()
> (should (go-boom)))
>
> And then:
> M-x eval-buffer RET
> M-x ert RET RET
>
> Result: The ERT window appears and shows that it is running the test.
> But it never shows that it finishes. Any tests that you have defined
> that follow test-go-boom in alphabetical order will not run. The echo
> area will show the message "Lisp nesting exceeds ‘max-lisp-eval-depth’"
This seems to have been fixed in the years since this bug was reported;
I get the result below, so I'm closing this bug report. If you're still
seeing this, please reopen.
-------
Selector: t
Passed: 0
Failed: 1 (1 unexpected)
Skipped: 0
Total: 1/1
Started at: 2019-07-27 14:24:49+0200
Finished.
Finished at: 2019-07-27 14:24:49+0200
F
F test-go-boom
(error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
24921 <at> debbugs.gnu.org and Gemini Lasswell <gazally <at> runbox.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 27 Jul 2019 12:27:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 25 Aug 2019 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 244 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.