From: Paul Eggert <eggert@cs.ucla.edu>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem)
Date: Thu, 23 Feb 2023 15:42:00 -0800 [thread overview]
Message-ID: <811d85e0-4032-68df-bc0c-1073ff5d1b96@cs.ucla.edu> (raw)
In-Reply-To: <f623bb2e-6f64-9f18-3e3c-512e7e5d88a0@cs.ucla.edu>
On 2/15/23 10:20, Paul Eggert wrote:
> On 2023-02-14 23:06, Jim Porter wrote:
>> Interesting. Running "./configure && make -j4 && make -j4 check" on
>> both Emacs master and the 29 branch shows these tests passing for me.
>
> I tried running it again on Ubuntu, several times, and this time
> server-tests.el succeeded. As you say, it may be a timing-related bug.
I tried running it on Fedora 37 x86-64 on a slow machine (AMD Phenom II
X4 910e) and reproduced the timing bug. The output of 'make check'
contained:
GEN lisp/server-tests.log
Running 7 tests (2023-02-23 09:45:51-0800, selector `(not (or (tag
:expensive-test) (tag :unstable) (tag :nativecomp)))')
make[3]: *** [Makefile:174: lisp/server-tests.log] Error 157
I guess "Error 157" means signal 29 (157 - 128), which is SIGIO on this
platform.
This was with Emacs master (commit
6411a9af03a4eb1a82db47a9642b11ba7edaaaf0).
next prev parent reply other threads:[~2023-02-23 23:42 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 [this message]
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
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=811d85e0-4032-68df-bc0c-1073ff5d1b96@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@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).