all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* bug#24921: 25.1; ERT fails to finish test run if test exceeeds max-lisp-eval-depth
@ 2016-11-10 17:55 Gemini Lasswell
  2019-07-27 12:26 ` Lars Ingebrigtsen
  0 siblings, 1 reply; 2+ messages in thread
From: Gemini Lasswell @ 2016-11-10 17:55 UTC (permalink / raw)
  To: 24921

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’"





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#24921: 25.1; ERT fails to finish test run if test exceeeds max-lisp-eval-depth
  2016-11-10 17:55 bug#24921: 25.1; ERT fails to finish test run if test exceeeds max-lisp-eval-depth Gemini Lasswell
@ 2019-07-27 12:26 ` Lars Ingebrigtsen
  0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2019-07-27 12:26 UTC (permalink / raw)
  To: Gemini Lasswell; +Cc: 24921

Gemini Lasswell <gazally@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





^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-07-27 12:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-10 17:55 bug#24921: 25.1; ERT fails to finish test run if test exceeeds max-lisp-eval-depth Gemini Lasswell
2019-07-27 12:26 ` Lars Ingebrigtsen

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.