public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Carl Love <cel@linux.ibm.com>,
	blarsen@redhat.com, gdb-patches@sourceware.org
Subject: Re: gdb.threads/attach-many-short-lived-threads.exp FAIL
Date: Tue, 5 Dec 2023 18:07:23 +0000	[thread overview]
Message-ID: <a17471ea-7fd2-424c-af17-cbca47ab3a7e@arm.com> (raw)
In-Reply-To: <8e771024d7ebbe9f36336a80312ea330f05e8a28.camel@linux.ibm.com>

On 12/5/23 18:01, Carl Love wrote:
> Luis, Guinevere:
> 
> I am also seeing a recent increase in the attach-many-short-lived-
> threads.exp test failures on both Power 9 and 10 buildbot results.  
> 
> I have seen a little "noise" in the past with a threads or signal test
> occasionally failing and then being fine on the next run.  I don't
> remember this particular test being noisy in the past.  But this test
> seems to have recently gotten really "noisy".
> 
> I saw that you both briefly discussed the failures on IRC.
> Here is what I am seeing for the attach-many-short-lived-threads.exp
> test failures.  The issues started on Friday Nov 31.
> 
>                	Power 9          	Power 10
> 11/31/2023	39 new fail, 1 fixed	0 new, 0 fixed
> 12/1/2023	0 new, 39 fixed		50 new, 0 fixed
> 12/2/2023	52 new, 0 fixed		87 new, 40 fixed
> 12/3/2023	checkout fail		12 new, 6 fixed
> 	
> I ran the full regression tests manually today.  It the attach-many-
> short-lived-threads.exp test ran fine on Power 9 and failed 103 times
> on Power 10.
> 
> I took a quick look at the git log and nothing jumped out as an obvious
> culprit.  It sounded like Luis was going to look into the test.  I
> thought I would start by reaching out to see what the status is?  Do we
> have a bugzilla for the issue?
> 
>                         Carl 
> 

I bisected these new FAIL's to a particular patch, and replied to this thread:

https://inbox.sourceware.org/gdb-patches/a6be03ef-9337-4693-a835-99ae5a0bc16e@arm.com/

      reply	other threads:[~2023-12-05 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 18:01 Carl Love
2023-12-05 18:07 ` Luis Machado [this message]

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=a17471ea-7fd2-424c-af17-cbca47ab3a7e@arm.com \
    --to=luis.machado@arm.com \
    --cc=blarsen@redhat.com \
    --cc=cel@linux.ibm.com \
    --cc=gdb-patches@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).