From: Paul Eggert <eggert@cs.ucla.edu>
To: 59061@debbugs.gnu.org
Cc: Philipp Stephani <phst@google.com>
Subject: bug#59061: bwrap-related Emacs test failure on Ubuntu 22.10
Date: Sat, 5 Nov 2022 14:39:02 -0700 [thread overview]
Message-ID: <382e75ec-ca0f-c4ae-4e98-fcebbbfb69ca@cs.ucla.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
This is on Ubuntu 22.10 x86-64, with current Emacs master (commit
8a49a888532c955ae81855636a65b446508cb361 dated today). "make check"
fails in some of the bubblewrap tests. Some bwrap expertise (which I
don't have) would be of use in debugging this so I'm taking the liberty
of cc'ing Philipp.
I'm attaching a copy of the build log (created with ./autogen.sh;
configure; make; make check) and of the test failure logged in
test/src/emacs-tests.log.
There are other test failures and if I get time I plan to file bug
reports for them too.
[-- Attachment #2: build-log.gz --]
[-- Type: application/gzip, Size: 31397 bytes --]
[-- Attachment #3: emacs-tests.log --]
[-- Type: text/x-log, Size: 2949 bytes --]
Running 7 tests (2022-11-05 12:11:07-0700, selector ‘(not (or (tag :expensive-test) (tag :unstable) (tag :nativecomp)))’)
Test emacs-tests/bwrap/allows-stdout backtrace:
signal(ert-test-failed (((should (eql status 0)) :form (eql 159 0) :
ert-fail(((should (eql status 0)) :form (eql 159 0) :value nil))
#f(compiled-function () #<bytecode 0x1ba5192d57495e9f>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name emacs-tests/bwrap/allows-stdout :docu
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ... ...))
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" "src/emacs-tests" "--eval"
command-line()
normal-top-level()
Test emacs-tests/bwrap/allows-stdout condition:
Info: Process output:
(ert-test-failed
((should
(eql status 0))
:form
(eql 159 0)
:value nil))
FAILED 1/7 emacs-tests/bwrap/allows-stdout (0.114432 sec) at src/emacs-tests.el:175
passed 2/7 emacs-tests/seccomp/absent-file (0.015406 sec)
Test emacs-tests/seccomp/allows-stdout backtrace:
signal(ert-test-failed (((should (eql status 0)) :form (eql "Bad sys
ert-fail(((should (eql status 0)) :form (eql "Bad system call" 0) :v
#f(compiled-function () #<bytecode -0xdcd8d3d483ef606>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name emacs-tests/seccomp/allows-stdout :do
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ... ...))
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" "src/emacs-tests" "--eval"
command-line()
normal-top-level()
Test emacs-tests/seccomp/allows-stdout condition:
Info: Process output:
(ert-test-failed
((should
(eql status 0))
:form
(eql "Bad system call" 0)
:value nil))
FAILED 3/7 emacs-tests/seccomp/allows-stdout (0.111244 sec) at src/emacs-tests.el:122
passed 4/7 emacs-tests/seccomp/empty-file (0.015778 sec)
passed 5/7 emacs-tests/seccomp/file-too-large (0.031031 sec)
passed 6/7 emacs-tests/seccomp/forbids-subprocess (0.111947 sec)
passed 7/7 emacs-tests/seccomp/invalid-file-size (0.015693 sec)
Ran 7 tests, 5 results as expected, 2 unexpected (2022-11-05 12:11:07-0700, 0.512199 sec)
2 unexpected results:
FAILED emacs-tests/bwrap/allows-stdout
FAILED emacs-tests/seccomp/allows-stdout
next reply other threads:[~2022-11-05 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:39 Paul Eggert [this message]
2022-11-17 0:26 ` bug#59061: bwrap-related Emacs test failure on Ubuntu 22.10 Matt Armstrong
2022-12-09 18:35 ` Philipp Stephani via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 12:33 ` Stefan Kangas
2022-12-09 18:44 ` Philipp Stephani via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=382e75ec-ca0f-c4ae-4e98-fcebbbfb69ca@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=59061@debbugs.gnu.org \
--cc=phst@google.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.