public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilfridge at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/30603] Various test failures with EPERM in systemd-nspawn container
Date: Sat, 22 Jul 2023 19:15:25 +0000	[thread overview]
Message-ID: <bug-30603-131-3ZPV6j2oCw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30603-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30603

Andreas K. Huettel <dilfridge at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.37                        |2.38
                 CC|                            |dilfridge at gentoo dot org

--- Comment #2 from Andreas K. Huettel <dilfridge at gentoo dot org> ---
aarch64 (jiji)

* baremetal

no failures

* in systemd-nspawn:

FAIL: misc/test-errno-linux
FAIL: misc/tst-mlock2
FAIL: misc/tst-ntp_gettime
FAIL: misc/tst-ntp_gettimex
FAIL: misc/tst-pkey
FAIL: misc/tst-process_mrelease
FAIL: time/tst-adjtime

Details from jiji:

FAIL: misc/test-errno-linux
> FAIL: mlock: errno is: 1 (Operation not permitted) expected one of LIST_FORWARD ({ 22, 12 })

FAIL: misc/tst-mlock2
> error: ../sysdeps/unix/sysv/linux/tst-mlock2.c:40: mlock: Operation not permitted
>
> error: 1 test failures

FAIL: misc/tst-ntp_gettime
> error: ../sysdeps/unix/sysv/linux/tst-ntp_gettime.c:46: NTP_GETTIME_SYSCALL failed: Operation not permitted
>
> error: 1 test failures

FAIL: misc/tst-ntp_gettimex
> error: ../sysdeps/unix/sysv/linux/tst-ntp_gettime.c:46: NTP_GETTIME_SYSCALL failed: Operation not permitted
>
> error: 1 test failures

FAIL: misc/tst-pkey
> error: ../sysdeps/unix/sysv/linux/tst-pkey.c:206: pkey_alloc: Operation not permitted
> error: 1 test failures

FAIL: misc/tst-process_mrelease
> ../sysdeps/unix/sysv/linux/tst-process_mrelease.c:54: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 9 (0x9); from: EBADF
> ../sysdeps/unix/sysv/linux/tst-process_mrelease.c:69: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 22 (0x16); from: EINVAL
> error: 2 test failures

FAIL: time/tst-adjtime
> error: tst-adjtime.c:38: adjtime (NULL, ...) failed: Operation not permitted
> error: 1 test failures

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-07-22 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-01 12:46 [Bug build/30603] New: " sam at gentoo dot org
2023-07-01 12:47 ` [Bug build/30603] " sam at gentoo dot org
2023-07-01 12:47 ` sam at gentoo dot org
2023-07-03  2:37 ` carlos at redhat dot com
2023-07-22 19:15 ` dilfridge at gentoo dot org [this message]
2023-07-22 19:31 ` dilfridge at gentoo dot org
2023-07-22 19:32 ` dilfridge at gentoo dot org
2023-07-27 13:58 ` gabravier at gmail dot com
2023-08-01 15:12 ` freswa at archlinux dot org

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=bug-30603-131-3ZPV6j2oCw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).