public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/30603] Various test failures with EPERM in systemd-nspawn container
Date: Mon, 03 Jul 2023 02:37:30 +0000 [thread overview]
Message-ID: <bug-30603-131-fbj7SBxLyP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30603-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30603
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Sam James from comment #0)
> One example of many is tst-ntp_gettimex:
> ```
> /var/tmp/portage/sys-libs/glibc-2.37-r3/work/build-hppa-hppa2.0-unknown-
> linux-gnu-nptl/misc/tst-ntp_gettimex.out
> ```
> error: ../sysdeps/unix/sysv/linux/tst-ntp_gettime.c:46: NTP_GETTIME_SYSCALL
> failed: Operation not permitted
>
> error: 1 test failures
> ```
Are you able to reproduce this under strace and determine the exact syscall
that is failing? Sometimes it's surprising what's failing.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-03 2:37 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 [this message]
2023-07-22 19:15 ` dilfridge at gentoo dot org
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-fbj7SBxLyP@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).