[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: server.el test failures (was: Re: bug#9800: Incomplete truncated fil
From: |
Paul Eggert |
Subject: |
Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem) |
Date: |
Sun, 26 Feb 2023 00:29:59 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
On 2023-02-23 16:50, Jim Porter wrote:
On 2/23/2023 3:42 PM, Paul Eggert wrote:
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).
Since the last message I posted, I'm now also seeing this test fail,
though I get a segfault instead. I bisected this to commit
a555abc56d5270cebe94f904189526d7ac433a94 ("Fix order of faces in
'face-list'").
Although I see a patch has been installed for that segfault, I'm still
seeing a server-tests.el failure of the original kind with SIGIO, this
time on a faster (though by no means bleeding edge) machine (a Xeon
W-1350) running Ubuntu 22.10 with current patches. This is with current
master (commit 8797e514ab68c12ed05d3af88e6baba64bf08f4d).
The SIGIO symptom this time contains a few more details, perhaps because
Ubuntu's shell is chattier than Fedora's:
/bin/bash: line 3: 2442869 I/O possible HOME=/nonexistent
LANG=C
EMACS_TEST_DIRECTORY=/home/eggert/src/gnu/emacs/static-checking/test
"../src/emacs" --module-assertions --no-init-file --no-site-file
--no-site-lisp -L ":." -l ert -l lisp/server-tests --batch --eval
'(ert-run-tests-batch-and-exit (quote (not (or (tag :expensive-test)
(tag :unstable) (tag :nativecomp)))))' > lisp/server-tests.log 2>&1
Running 7 tests (2023-02-26 00:13:56-0800, selector ‘(not (or (tag
:expensive-test) (tag :unstable) (tag :nativecomp)))’)
make[3]: *** [Makefile:174: lisp/server-tests.log] Error 157
I'm also getting a failure with mule-tests:
Test sgml-html-meta-no-post-less-than-10lines backtrace:
signal(ert-test-failed (((should (eq 'utf-8 (sgml-html-meta-run (con
ert-fail(((should (eq 'utf-8 (sgml-html-meta-run (concat "\n\n\n\n\n
#f(compiled-function () #<bytecode -0x1e01a52764337803>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name sgml-html-meta-no-post-less-than-10li
ert-run-or-rerun-test(#s(ert--stats :selector (not ...) :tests [...
ert-run-tests((not (or (tag :expensive-test) (tag :unstable) (tag :n
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable) (
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/international/mule-t
command-line()
normal-top-level()
Test sgml-html-meta-no-post-less-than-10lines condition:
(ert-test-failed
((should
(eq 'utf-8
(sgml-html-meta-run ...)))
:form
(eq utf-8 utf-8-unix)
:value nil))
FAILED 7/13 sgml-html-meta-no-post-less-than-10lines (0.000100
sec) at lisp/international/mule-tests.el:119
passed 8/13 sgml-html-meta-no-pre (0.000154 sec)
passed 9/13 sgml-html-meta-none (0.000086 sec)
Warning: unknown coding system "XXX"
passed 10/13 sgml-html-meta-unknown-coding (0.000092 sec)
passed 11/13 sgml-html-meta-utf-8 (0.000073 sec)
passed 12/13 sgml-html-meta-utf-8-with-bom (0.000072 sec)
passed 13/13 sgml-html-meta-windows-hebrew (0.000071 sec)
Ran 13 tests, 12 results as expected, 1 unexpected (2023-02-26
00:13:53-0800, 0.073256 sec)
1 unexpected results:
FAILED sgml-html-meta-no-post-less-than-10lines
make[3]: *** [Makefile:174: lisp/international/mule-tests.log] Error 1
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), (continued)
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Eli Zaretskii, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Jim Porter, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Eli Zaretskii, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Alan Mackenzie, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Jim Porter, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Eli Zaretskii, 2023/02/24
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem),
Paul Eggert <=
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Eli Zaretskii, 2023/02/26
- Re: server.el test failures (was: Re: bug#9800: Incomplete truncated file buffers from the /proc filesystem), Jim Porter, 2023/02/27
- Re: server.el test failures, Robert Pluim, 2023/02/27
- Re: server.el test failures, Eli Zaretskii, 2023/02/27
- Re: server.el test failures, Robert Pluim, 2023/02/27
- Re: server.el test failures, Eli Zaretskii, 2023/02/27
- Re: server.el test failures, Robert Pluim, 2023/02/28
- Re: server.el test failures, Eli Zaretskii, 2023/02/28
- Re: server.el test failures, Robert Pluim, 2023/02/28
- Re: server.el test failures, Jim Porter, 2023/02/28