From: Philipp Stephani via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Matt Armstrong <matt@rfc20.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 59061@debbugs.gnu.org
Subject: bug#59061: bwrap-related Emacs test failure on Ubuntu 22.10
Date: Fri, 9 Dec 2022 19:35:53 +0100 [thread overview]
Message-ID: <CAP-RRPv7NkLxWMLRmjbKgcAMx0kWBCzkhUjxMSKq9V9PAGvcQQ@mail.gmail.com> (raw)
In-Reply-To: <87y1sas9xl.fsf@rfc20.org>
On Thu, 17 Nov 2022 at 01:26, Matt Armstrong <matt@rfc20.org> wrote:
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > 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.
>
> I was able to reproduce this on a Debian Testing system after installing
> the "libseccomp-dev" package. The test failures I get are identical to
> Paul's.
>
> Without that package lib-src/Makefile refrains from building
> lib-src/seccomp-filter.bpf, which in turn causes these tests to be
> skipped. This may explain why chatter about these failures has been
> low.
I've now tried to fix this with commit 940d9070e97858fdb6c0d84fc5617b8c10dab0ba.
--
Google Germany GmbH
Erika-Mann-Straße 33
80636 München
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise
erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes
weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich
bitte wissen, dass die E-Mail an die falsche Person gesendet wurde.
This e-mail is confidential. If you received this communication by
mistake, please don’t forward it to anyone else, please erase all
copies and attachments, and please let me know that it has gone to the
wrong person.
next prev parent reply other threads:[~2022-12-09 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:39 bug#59061: bwrap-related Emacs test failure on Ubuntu 22.10 Paul Eggert
2022-11-17 0:26 ` Matt Armstrong
2022-12-09 18:35 ` Philipp Stephani via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=CAP-RRPv7NkLxWMLRmjbKgcAMx0kWBCzkhUjxMSKq9V9PAGvcQQ@mail.gmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59061@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=matt@rfc20.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.