From: Andrew Burgess <aburgess@redhat.com>
To: Keith Seitz <keiths@redhat.com>,
Guinevere Larsen <blarsen@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: make gdb_get_worker_threads reads default number of threads
Date: Wed, 06 Dec 2023 16:22:12 +0000 [thread overview]
Message-ID: <878r67gv2j.fsf@redhat.com> (raw)
In-Reply-To: <481d8b16-8e3f-45aa-9c01-ed398bb63dd5@redhat.com>
Keith Seitz <keiths@redhat.com> writes:
> Hi,
>
> On 12/5/23 07:26, Guinevere Larsen wrote:
>
>> One such example is the current buildbot instance (at least the clang
>> version). This commit adds a new clause to the gdb_get_worker_threads
>> that detects the default worker thread message.
>> ---
>> gdb/testsuite/lib/gdb.exp | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
>> index d0990dcfe0e..148476cf42d 100644
>> --- a/gdb/testsuite/lib/gdb.exp
>> +++ b/gdb/testsuite/lib/gdb.exp
>> @@ -10034,6 +10034,9 @@ proc gdb_get_worker_threads { {testname ""} } {
>> -wrap -re "^The number of worker threads GDB can use is unlimited \\(currently ($::decimal)\\)\\." {
>> set worker_threads $expect_out(1,string)
>> }
>> + -wrap -re "^The number of worker threads GDB can use is the default \\(currently ($::decimal)\\)\\." {
>> + set worker_threads $expect_out(1,string)
>> + }
>> -wrap -re "^The number of worker threads GDB can use is ($::decimal)\\." {
>> set worker_threads $expect_out(1,string)
>> }
>
> This is new:
>
> 33ae45434d0ab1f7de365b9140ad4e4ffc34b8a2
> Date: Mon Dec 4 14:23:17 2023 +0000
>
> gdb: Enable early init of thread pool size
>
> That commit changes the "is unlimited" text from
> maintenance_show_worker_threads to "is the default":
>
> gdb_printf (file, _("The number of worker threads GDB "
> - "can use is unlimited (currently %zu).\n"),
> + "can use is the default (currently %zu).\n"),
> gdb::thread_pool::g_thread_pool->thread_count ());
>
> So this patch can be further simplified. Otherwise LGTM.
Indeed. This was my mistake for not retesting after the final rebase.
As Keith said s/unlimited/the default/ instead of adding a whole new
regexp, and this is good to go.
Approved-By: Andrew Burgess <aburgess@redhat.com>
Thanks,
Andrew
next prev parent reply other threads:[~2023-12-06 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:26 Guinevere Larsen
2023-12-05 21:45 ` Keith Seitz
2023-12-06 16:22 ` Andrew Burgess [this message]
2023-12-06 16:35 ` Tom de Vries
2023-12-06 15:39 ` Tom Tromey
2023-12-06 15:44 ` Guinevere Larsen
2023-12-06 16:33 ` Richard Bunt
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=878r67gv2j.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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).