public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "freswa at archlinux dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/29485] New: Make hangs when the test misc/tst-pidfile returns FAIL_UNSUPPORTED Date: Sun, 14 Aug 2022 00:46:14 +0000 [thread overview] Message-ID: <bug-29485-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29485 Bug ID: 29485 Summary: Make hangs when the test misc/tst-pidfile returns FAIL_UNSUPPORTED Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: freswa at archlinux dot org CC: carlos at redhat dot com Target Milestone: --- Created attachment 14275 --> https://sourceware.org/bugzilla/attachment.cgi?id=14275&action=edit Patch fixing the bug Arch Linux builds glibc in a systemd-nspawn. To avoid issues with the testsuite, we disable some tests that require syscalls not allowed by nspawn. Commit (bisected) 325ba824b0611e14e96b38dbc486acf255f9e568 introduced a hang of make after printing the test summary at the end. The root cause in sysdeps/unix/sysv/linux/tst-pidfd.c is the early return in line 150 which is causing the process, spawned in line 46, to hang on line 84 waiting for the signal in line 170. Patch attached. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-08-14 0:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-14 0:46 freswa at archlinux dot org [this message] 2022-08-14 21:39 ` [Bug build/29485] " sam at gentoo dot org 2022-08-14 21:39 ` sam at gentoo dot org 2022-08-15 5:39 ` fweimer at redhat dot com 2022-08-15 9:23 ` mark at klomp 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-29485-131@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: linkBe 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).