all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 47708@debbugs.gnu.org
Subject: bug#47708: 28.0.50; SIGSYS test failure with seccomp-filter.bpf
Date: Sun, 11 Apr 2021 15:58:57 +0200	[thread overview]
Message-ID: <CAArVCkQHUn09ciZ=ehoww3GJe375MPkth-bTEVAsSqQBEERwow@mail.gmail.com> (raw)
In-Reply-To: <87r1jharjy.fsf@tcd.ie>

Am So., 11. Apr. 2021 um 15:19 Uhr schrieb Basil L. Contovounesios
<contovob@tcd.ie>:
>
> On Debian Testing with libseccomp 2.5.1-1, 'make test/emacs-tests' fails
> with:
>
>   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
>     [...]
>     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  2/6  emacs-tests/seccomp/allows-stdout (0.032159 sec)
>

Thanks for the report! Could you check which syscall exactly is
failing, e.g. using
journalctl -g SECCOMP -t audisp-syslog
(assuming that system uses systemd and seccomp audit logging is enabled).





  reply	other threads:[~2021-04-11 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 13:17 bug#47708: 28.0.50; SIGSYS test failure with seccomp-filter.bpf Basil L. Contovounesios
2021-04-11 13:58 ` Philipp Stephani [this message]
2021-04-11 17:13   ` Basil L. Contovounesios
2021-04-11 17:19     ` Basil L. Contovounesios
2021-04-11 17:52       ` Philipp Stephani
2021-04-11 18:49         ` Basil L. Contovounesios
2021-04-11 17:39     ` Philipp Stephani

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='CAArVCkQHUn09ciZ=ehoww3GJe375MPkth-bTEVAsSqQBEERwow@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=47708@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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.