From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55628@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#55628: debug-timer-check fails on macOS 11.6.6
Date: Thu, 26 May 2022 15:15:56 +0200 [thread overview]
Message-ID: <2508D80D-E65A-4407-A09C-8E1A2E8E80AF@acm.org> (raw)
In-Reply-To: <837d68plsk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
26 maj 2022 kl. 13.37 skrev Eli Zaretskii <eliz@gnu.org>:
> Not in principle, but we in this project don't do that. E.g., there
> are several debug-related functions and commands in xdisp.c that are
> only compiled in under ENABLE_CHECKING.
I don't think that not having done it in the past is justification enough for not doing it now, but I agree that it would be preferable to have it covered by a test that doesn't need a special interface.
It looks like funcall-with-delayed-message could be used for this purpose. I came up with the attached test, which also has the benefit of extending test coverage to that function which previously had none.
[-- Attachment #2: funcall-with-delayed-message-test.diff --]
[-- Type: application/octet-stream, Size: 1510 bytes --]
diff --git a/test/src/eval-tests.el b/test/src/eval-tests.el
index e4230c10ef..1b2ad99360 100644
--- a/test/src/eval-tests.el
+++ b/test/src/eval-tests.el
@@ -240,4 +240,31 @@ eval-tests/backtrace-in-batch-mode/demoted-errors
(should (equal (string-trim (buffer-string))
"Error: (error \"Boo\")")))))
+(ert-deftest eval-tests/funcall-with-delayed-message ()
+ ;; Check that `funcall-with-delayed-message' displays its message before
+ ;; its function terminates iff the timeout is short enough.
+
+ ;; This also serves as regression test for bug#55628 where a short
+ ;; timeout was rounded up to the next whole second.
+ (dolist (params '((0.8 0.4)
+ (0.1 0.8)))
+ (let ((timeout (nth 0 params))
+ (work-time (nth 1 params)))
+ (ert-info ((prin1-to-string params) :prefix "params: ")
+ (with-current-buffer "*Messages*"
+ (let ((inhibit-read-only t))
+ (erase-buffer))
+ (let ((stop (+ (float-time) work-time)))
+ (funcall-with-delayed-message
+ timeout "timed out"
+ (lambda ()
+ (while (< (float-time) stop))
+ (message "finished"))))
+ (let ((expected-messages
+ (if (< timeout work-time)
+ "timed out\nfinished"
+ "finished")))
+ (should (equal (string-trim (buffer-string))
+ expected-messages))))))))
+
;;; eval-tests.el ends here
next prev parent reply other threads:[~2022-05-26 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 10:46 bug#55628: debug-timer-check fails on macOS 11.6.6 Mattias Engdegård
2022-05-25 12:20 ` Lars Ingebrigtsen
2022-05-25 13:05 ` Mattias Engdegård
2022-05-25 14:02 ` Eli Zaretskii
2022-05-25 15:34 ` Mattias Engdegård
2022-05-25 17:11 ` Eli Zaretskii
2022-05-26 9:57 ` Mattias Engdegård
2022-05-26 11:37 ` Eli Zaretskii
2022-05-26 13:15 ` Mattias Engdegård [this message]
2022-05-30 10:43 ` Mattias Engdegård
2022-05-30 13:42 ` Lars Ingebrigtsen
2022-05-30 13:55 ` Mattias Engdegård
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=2508D80D-E65A-4407-A09C-8E1A2E8E80AF@acm.org \
--to=mattiase@acm.org \
--cc=55628@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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).