GNU bug report logs - #58877
29.0.50; [PATCH] When killing Emacs from a client frame with no other frames, Emacs shows a useless error prompt

Previous Next

Package: emacs;

Reported by: Jim Porter <jporterbugs <at> gmail.com>

Date: Sat, 29 Oct 2022 21:34:02 UTC

Severity: normal

Tags: patch

Found in version 29.0.50

Done: Jim Porter <jporterbugs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: 58877 <at> debbugs.gnu.org
Subject: Re: bug#58877: 29.0.50; [PATCH] When killing Emacs from a client
 frame with no other frames, Emacs shows a useless error prompt
Date: Fri, 25 Nov 2022 15:25:36 +0200
> Date: Thu, 24 Nov 2022 17:36:11 -0800
> Cc: 58877-done <at> debbugs.gnu.org
> From: Jim Porter <jporterbugs <at> gmail.com>
> 
> Merged as 28c444f72a9843ce335032db1fa0f484dfeb4833 with the typo fixed. 

Thanks.

Are the tests supposed to be portable?  Here on MS-Windows 5 tests fail:

  5 unexpected results:
     FAILED  server-tests/emacsclient/create-frame
     FAILED  server-tests/emacsclient/eval
     FAILED  server-tests/emacsclient/server-edit
     FAILED  server-tests/server-force-stop/keeps-frames
     FAILED  server-tests/server-start/stop-prompt-with-client

All of them fail due to some timeout:

  Test server-tests/emacsclient/create-frame backtrace:
    signal(ert-test-failed ("timed out waiting for (length= (frame-list)
    ert-fail("timed out waiting for (length= (frame-list) 2) to ...")

so this sounds like some fundamental issue common to all those tests.

On GNU/Linux all the tests pass.

Let me know if you want me to investigate something.




This bug report was last modified 2 years and 170 days ago.

Previous Next


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