From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: server.el test failures Date: Mon, 27 Feb 2023 18:50:20 +0200 Message-ID: <83ttz7giib.fsf@gnu.org> References: <877h40vb8h.fsf@mail.jurta.org> <4EA4D31B.4050604@cs.ucla.edu> <4EA5E08D.8070903@cs.ucla.edu> <861qmvcglp.fsf@aarsen.me> <98e880a0-d076-cfd9-b39d-50c84fa8975a@gmail.com> <811d85e0-4032-68df-bc0c-1073ff5d1b96@cs.ucla.edu> <5a38c18d-263c-223b-7335-8395a10eb494@gmail.com> <00864fe6-b63a-685f-2d20-4e1fd5a5573e@cs.ucla.edu> <3e7c26d6-215a-6c29-5304-0e32f42b2174@gmail.com> <87zg8z5afj.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40363"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 27 17:51:44 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWgj2-000AHJ-1V for ged-emacs-devel@m.gmane-mx.org; Mon, 27 Feb 2023 17:51:44 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pWghs-0000Db-Uh; Mon, 27 Feb 2023 11:50:32 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWghq-0000C4-Uz for emacs-devel@gnu.org; Mon, 27 Feb 2023 11:50:30 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWghp-0000eW-Ro; Mon, 27 Feb 2023 11:50:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=3zJimUoe1kbfZt2iPtBMj/XsanzCKaw1nE8jRvEL7qA=; b=niHQknsS/yQU tU/62TZDgTzu/xyytwhdhttcigNZO7M7o6oQ3/xvDMLesPgvJL6d05iLrcjt3ye67kAqaiTARRDn7 VLInUHsEdvKw5I3lC8ACZ1zZECQU0HwY6LmYCZ2FNROnDZ/gc+E34+JARbuCd3loxfd64l7cvcj7T eWlflC997OhwvarQK7Luaewaqw4FMhBHex1YrjpoJOTLXzeok6alCbD/XdRyhxKUDeckzNl3jcEbq fAeL9BYZOBLJnsDHN1Osdcp9y8BKyGsjxpbnSFUnVjhQ0Zvqgw7m58jK/D0qA2s52B/bpMkO689Yj MEZRhpNTA9c9tVPoGXpW6w==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWghY-00033I-83; Mon, 27 Feb 2023 11:50:29 -0500 In-Reply-To: <87zg8z5afj.fsf@gmail.com> (message from Robert Pluim on Mon, 27 Feb 2023 17:40:16 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303837 Archived-At: > From: Robert Pluim > Cc: Paul Eggert , emacs-devel@gnu.org > Date: Mon, 27 Feb 2023 17:40:16 +0100 > > I can make server-tests fail 100% on master and emacs-29 on Debian by > running the tests from inside emacs using vterm. I commented out all > the tests except server-tests/server-force-stop/keeps-frames > > make -C test server-tests > make: Entering directory '/home/rpluim/repos/emacs/test' > make[1]: Entering directory '/home/rpluim/repos/emacs/test' > ELC lisp/server-tests.elc > GEN lisp/server-tests.log > Running 1 tests (2023-02-27 17:35:01+0100, selector `(not (or (tag :unstable) (tag :nativecomp)))') > make[1]: *** [Makefile:174: lisp/server-tests.log] I/O possible > make[1]: Leaving directory '/home/rpluim/repos/emacs/test' > make: *** [Makefile:240: lisp/server-tests] Error 2 > make: Leaving directory '/home/rpluim/repos/emacs/test' > rltb:~/repos/emacs (master *)> It's probably bogus, or the test is unstable, but just so we don't give up easily: can you show a C and Lisp backtrace from the SIGIO signal handler when it gets the signal in this case?