bug#47828: seccomp test failures

[Philipp Stephani <p.stephani2@gmail.com>]

Am Sa., 17. Apr. 2021 um 20:21 Uhr schrieb Philipp Stephani
<p.stephani2@gmail.com>:
>
> Am Fr., 16. Apr. 2021 um 19:59 Uhr schrieb Glenn Morris <rgm@gnu.org>:
> >
> > Package: emacs
> > Version: 28.0.50
> >
> > On CentOS 8.3 at fb9f5501:
> >
> > Test emacs-tests/bwrap/allows-stdout condition:
> >     Info: Process output:
> >     (ert-test-failed
> >      ((should
> >        (eql status 0))
> >       :form
> >       (eql 159 0)
> >       :value nil))
> >
> > 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))
>
>
> Thanks for the report, could you check which syscall failed, e.g. by
> checking the kernel audit logs or by posting a stacktrace for the
> failure?

FYI, I've now pushed commit 568ce6826fa0aaa4d5dc95880cbdc0965dc07521
to master which attempts to automatically collect this information to
ease debugging such failures.