public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@linux.ibm.com>
To: Tom Tromey <tom@tromey.com>, Carl Love <cel@linux.ibm.com>
Cc: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Update xfail in gdb.threads/attach-many-short-lived-threads.exp
Date: Tue, 6 Feb 2024 11:03:51 -0800	[thread overview]
Message-ID: <e7d86585-2668-493d-bc5b-701c19cd7889@linux.ibm.com> (raw)
In-Reply-To: <62621485-1f8f-471e-a3ec-2c6e03ff2610@linux.ibm.com>

Tom:

So I have spent some more time playing with this test.  I have played with adjusting the timeout with no clear improvement in the reliability of the test.

I see that once we hit the EPERM failure, the test skips the tests for the rest of that iteration and then tries to attach again to the same testpid on the next iteration of the test loop.  On Power 10, this results in a timeout on the attach and all the rest of the gdb commands timeout for all subsequent test loop iterations.  So depending on which iteration the error occurs on you get a different number of failures from run to run.

So, it seems like we need handle the EPERM error differently from what is currently being done.  I can think of
three possible ways to handle the error, as I put into the latest update of the issue.  If you have any other ideas on how we could handle the EPERM failures please let me know.  My third suggestion does seem to fix the test but I have to say I am not entirely happy with that fix.

https://sourceware.org/bugzilla/show_bug.cgi?id=31312

Please add your thoughts on my solution and any additional solutions to the bugzilla.  Thanks for your help on this issue.

                        Carl 

      reply	other threads:[~2024-02-06 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 23:18 Tom de Vries
2024-01-19 16:27 ` Tom Tromey
2024-01-24 18:51   ` Carl Love
2024-01-24 20:47     ` Carl Love
2024-01-26 16:13       ` Carl Love
2024-01-29 17:04         ` Tom Tromey
2024-01-29 18:13           ` Carl Love
2024-02-06 19:03             ` Carl Love [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=e7d86585-2668-493d-bc5b-701c19cd7889@linux.ibm.com \
    --to=cel@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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).