From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3142E3858C35; Tue, 14 May 2024 15:24:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3142E3858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1715700288; bh=dXskpNS34Ev70LWdoVThvINkTzCAhaxbuqgIjeuvD68=; h=From:To:Subject:Date:In-Reply-To:References:From; b=N8Id+ldhNeUSXBL31oqAhs6jZ9k4CSU/fvhDnJ3uP0ZJozzvnnVPjhhCAtxVB9z2/ jMGr6VLwkWFCMCi734RQrAyEYUflBsYTJZhpOLa6y1ZwvE/RR3Kfn0VkD4SIGww5jU f8TulL2DAH/ZQ56vtMcBgX2BuYv3CSlSm7a/ncS0= From: "cel at linux dot ibm.com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31312] attach-many-short-lived-threads gives inconsistent results Date: Tue, 14 May 2024 15:24:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cel at linux dot ibm.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: cel at linux dot ibm.com X-Bugzilla-Target-Milestone: 15.1 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=3D31312 --- Comment #33 from Carl E Love --- So, just when we claimed it was fixed, I started getting errors again. The test has been running fine for several weeks and then yesterday after we ta= lked about closing the issue I got errors. I got errors again today: ** 64 bit checkout OK GIT commit id: a2db92ea312564431917ffab35ed927ea5b24201 build OK installation OK 24 failures 0 new failures 24 old failures fixed -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 10: break at break_fn: 1 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 10: break at break_fn: 2 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 10: break at break_fn: 3 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 10: kill proce= ss -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 6: break at break_fn: 1 -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 6: break at break_fn: 2 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 6: break at break_fn: 3 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 6: detach (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 6: reset timer= in the inferior -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 7: break at break_fn: 1 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 7: break at break_fn: 2 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 7: break at break_fn: 3 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 7: detach (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 7: reset timer= in the inferior -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 8: break at break_fn: 1 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 8: break at break_fn: 2 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 8: break at break_fn: 3 (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 8: detach (the program is no longer running) -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 8: reset timer= in the inferior -FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 9: break at break_fn: 1 (the program is no longer running)=20 I don't see any changes to attach-many-short-lived-threads.exp. However, it does look like the system was moved to new hardware a couple of days ago. I would have to guess that has something to do with the failures= . I will have to look into it some more. --=20 You are receiving this mail because: You are on the CC list for the bug.=