Re: server.el test failures

[Eli Zaretskii <eliz@gnu.org>]

> From: Robert Pluim <rpluim@gmail.com>
> Cc: jporterbugs@gmail.com,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
> Date: Mon, 27 Feb 2023 19:14:54 +0100
> 
>     Eli> It's probably bogus, or the test is unstable, but just so we don't
>     Eli> give up easily: can you show a C and Lisp backtrace from the SIGIO
>     Eli> signal handler when it gets the signal in this case?
> 
> Iʼd love to, but our signal handler never gets called:
> 
> (gdb) b deliver_process_signal
> Breakpoint 3 at 0x19d47e: deliver_process_signal. (2 locations)
> (gdb) r
> Starting program: /home/rpluim/repos/emacs/src/emacs --module-assertions --no-init-file --no-site-file --no-site-lisp -L "
> :."  \
>   -l ert  -l lisp/server-tests.el \
>   --batch --eval '(ert-run-tests-batch-and-exit (quote (not (or (tag :unstable) (
> tag :nativecomp)))))' 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7ffff129d700 (LWP 783192)]
> Running 1 tests (2023-02-27 18:45:41+0100, selector `(not (or (tag :unstable) (tag :nativecomp)))')
> [Detaching after vfork from child process 783193]
> [New Thread 0x7ffff0992700 (LWP 783194)]
> [New Thread 0x7fffeba46700 (LWP 783195)]
> [Thread 0x7fffeba46700 (LWP 783195) exited]
> [Thread 0x7ffff129d700 (LWP 783192) exited]
> [Thread 0x7ffff22f8040 (LWP 783187) exited]
> 
> Program terminated with signal SIGIO, I/O possible.
> The program no longer exists.

What does "handle SIGIO" say before you type "run"?  Try this:

  (gdb) handle SIGIO stop print

and then run the test in batch mode again.