Subject: bug#59742: closed (Re: bug#59742: server-tests failures)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 03 Dec 2022 15:21:02 +0000

Your bug report

#59742: server-tests failures

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
59742: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59742
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#59742: server-tests failures
From: Mattias Engdegård <[email-masked]>
To: Jim Porter <[email-masked]>
Cc: [email-masked]
Date: Sat, 3 Dec 2022 16:20:21 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

> Let's see how the CI takes it.

Looks like it's happy now. Closing now, but do tell if you have misgivings.

Subject: server-tests failures
From: Mattias Engdegård <[email-masked]>
To: Emacs Bug Report <[email-masked]>
Cc: Jim Porter <[email-masked]>
Date: Thu, 1 Dec 2022 16:01:45 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

The server-tests still fail for an apparent variety of reasons. The behaviour differs depending how the test is run: from a terminal, from ´M-x compile`, interactively via `M-x ert`, Emacs started with or without `-nw`, and so on.

At least the batch-mode tests would cease failing if we just applied the following:

 (defconst server-tests/can-create-frames-p
-  (not (memq system-type '(windows-nt ms-dos)))
+  (and window-system (not (memq system-type '(windows-nt ms-dos))))

Any reason not to?

Even so, there is still a failure if run interactively (M-x ert), and a created frame isn't removed properly.