[gnutls-devel] [tests] seccomp fails

[Nikos Mavrogiannopoulos]

Could it be a switch of the system call used by glibc? Does strace provide
more info on the blocked call?

On Mon, May 7, 2018 at 8:15 AM, Alon Bar-Lev <alon.barlev at gmail.com> wrote:

> Hi,
>
> The seccomp tests are failing, I am almost sure these worked in the past.
>
> FAIL: dtls-with-seccomp
> FAIL: tls-with-seccomp
> FAIL: dtls-client-with-seccomp
> FAIL: tls-client-with-seccomp
>
> Attached a log for example. Any clue? I cannot see anything I can decipher.
>
> Kernel 4.9.95 has CONFIG_SECCOMP=y
> sys-libs/libseccomp-2.3.2.
>
> Thanks!
>
>
> _______________________________________________
> Gnutls-devel mailing list
> Gnutls-devel at lists.gnutls.org
> http://lists.gnupg.org/mailman/listinfo/gnutls-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20180507/a4130280/attachment.html>