From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 031583858D28; Tue, 27 Jun 2023 14:58:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 031583858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1687877924; bh=jMhHiR0cdaeUQGhjHkqqlmgR4qhQS0avxuSWRKTnC1w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UwRxaaTWj3zo5I6WTYhcI7IwlPRWIXw8jYV2cT3WmGQnFXFkUtq3KaKVsoaeebgb3 X00jx19UMnzgqlxQcqm5WR59x3G+/yFsNWxUKwikt/6uhFcK592G0C2exY2VOM6RkK 7N5sRmMTYhtpMJJI7OuM/OAJJCah7MRjUr9d96xs= From: "dave.anglin at bell dot net" To: glibc-bugs@sourceware.org Subject: [Bug nptl/30587] FAIL: nptl/tst-cleanupx4 on hppa Date: Tue, 27 Jun 2023 14:58:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dave.anglin at bell dot net X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30587 --- Comment #3 from dave.anglin at bell dot net --- On 2023-06-27 10:08 a.m., fberat at redhat dot com wrote: > In principle, we could revert the change affecting nptl/tst-cleanup.c but= I'm a > bit puzzled by this issue. It looks strange that it affects nptl/tst-clea= nupx4 > but not nptl/tst-cleanup4. The only difference between the 2 being the li= nkage. Correct, only nptl/tst-cleanupx4 fails after change. --=20 You are receiving this mail because: You are on the CC list for the bug.=