From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: jporterbugs@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: server.el test failures
Date: Mon, 27 Feb 2023 18:50:20 +0200 [thread overview]
Message-ID: <83ttz7giib.fsf@gnu.org> (raw)
In-Reply-To: <87zg8z5afj.fsf@gmail.com> (message from Robert Pluim on Mon, 27 Feb 2023 17:40:16 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 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?
next prev parent reply other threads:[~2023-02-27 16:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877h40vb8h.fsf@mail.jurta.org>
[not found] ` <4EA4D31B.4050604@cs.ucla.edu>
[not found] ` <E1RISPO-0007Eu-TE@fencepost.gnu.org>
[not found] ` <4EA5E08D.8070903@cs.ucla.edu>
[not found] ` <861qmvcglp.fsf@aarsen.me>
[not found] ` <f711f43f-6892-f849-21ec-26376c351f11@cs.ucla.edu>
2023-02-13 21:55 ` server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem) Jim Porter
2023-02-14 2:47 ` Paul Eggert
2023-02-15 7:06 ` Jim Porter
2023-02-15 18:20 ` Paul Eggert
2023-02-23 23:42 ` Paul Eggert
2023-02-24 0:50 ` Jim Porter
2023-02-24 2:20 ` Jim Porter
2023-02-24 3:25 ` Po Lu
2023-02-24 3:38 ` Jim Porter
2023-02-24 7:52 ` Eli Zaretskii
2023-02-24 17:48 ` Jim Porter
2023-02-24 18:37 ` Eli Zaretskii
2023-02-24 19:45 ` Alan Mackenzie
2023-02-24 20:31 ` Jim Porter
2023-02-24 20:47 ` Eli Zaretskii
2023-02-26 8:29 ` Paul Eggert
2023-02-26 9:47 ` Eli Zaretskii
2023-02-27 5:31 ` Jim Porter
2023-02-27 16:40 ` server.el test failures Robert Pluim
2023-02-27 16:50 ` Eli Zaretskii [this message]
2023-02-27 18:14 ` Robert Pluim
2023-02-27 18:39 ` Eli Zaretskii
2023-02-28 7:42 ` Robert Pluim
2023-02-28 12:13 ` Eli Zaretskii
2023-02-28 13:05 ` Robert Pluim
2023-02-28 19:02 ` Jim Porter
2023-02-28 19:23 ` Eli Zaretskii
2023-02-28 19:41 ` Jim Porter
2023-03-01 8:22 ` Robert Pluim
2023-03-02 22:15 ` Jim Porter
2023-03-03 7:00 ` Eli Zaretskii
2023-03-03 7:15 ` Jim Porter
2023-03-03 8:00 ` Jim Porter
2023-03-03 8:10 ` Eli Zaretskii
2023-03-03 17:27 ` Jim Porter
2023-03-03 8:16 ` Robert Pluim
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=83ttz7giib.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=rpluim@gmail.com \
/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).