public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] [gdb/testsuite] Use unique portnum in parallel testing (check//% case)
Date: Sat, 4 May 2024 09:48:26 +0200	[thread overview]
Message-ID: <9cdcd951-fc44-48fd-afb7-f9445c1b67da@suse.de> (raw)
In-Reply-To: <87bk5mbpuq.fsf@tromey.com>

On 5/3/24 22:30, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
> 
> Tom> Fix this by:
> Tom> - creating a common lockdir build/gdb/testsuite.lockdir for make target
> Tom>   check//%,
> Tom> - passing this down to the runtests invocations using variable GDB_LOCK_DIR,
> Tom>   and
> Tom> - using GDB_LOCK_DIR in lock_dir.
> 
> I think I've never once used check//.
> I'm not even sure I was aware of its existence.
> 

I know it from the suse / opensuse gdb package ( 
https://build.opensuse.org/projects/devel:gcc/packages/gdb/files/gdb.spec?expand=1 
), which I think inherited it from the fedora gdb package.

> Tom>  proc lock_dir {} {
> Tom> +    if { [info exists ::GDB_LOCK_DIR] } {
> Tom> +	# When using check//.
> Tom> +	return $::GDB_LOCK_DIR
> Tom> +    }
> Tom> +
> Tom>      return [make_gdb_parallel_path cache]
> Tom>  }
> 
> I guess this approach of not always requiring GDB_LOCK_DIR is handy when
> running runtest by hand... I was thinking it might be better to unify
> all the scenarios here, but really this doesn't seem so complicated.
> 
> Approved-By: Tom Tromey <tom@tromey.com>
> 

Thanks for the review, I'll commit after a round of retesting.

Thanks,
- Tom


  reply	other threads:[~2024-05-04  7:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 15:56 [PATCH 1/7] [gdb/testsuite] Factor out proc get_portnum Tom de Vries
2024-04-15 15:56 ` [PATCH 2/7] [gdb/testsuite] Make portnum a persistent global Tom de Vries
2024-05-03 20:20   ` Tom Tromey
2024-04-15 15:56 ` [PATCH 3/7] [gdb/testsuite] Factor out proc with_lock Tom de Vries
2024-05-03 20:22   ` Tom Tromey
2024-04-15 15:56 ` [PATCH 4/7] [gdb/testsuite] Factor out proc lock_dir Tom de Vries
2024-05-03 20:23   ` Tom Tromey
2024-04-15 15:56 ` [PATCH 5/7] [gdb/testsuite] Move gpu-parallel.lock to cache dir Tom de Vries
2024-05-03 20:25   ` Tom Tromey
2024-04-15 15:56 ` [PATCH 6/7] [gdb/testsuite] Use unique portnum in parallel testing Tom de Vries
2024-05-03 20:27   ` Tom Tromey
2024-04-15 15:56 ` [PATCH 7/7] [gdb/testsuite] Use unique portnum in parallel testing (check//% case) Tom de Vries
2024-05-03 20:30   ` Tom Tromey
2024-05-04  7:48     ` Tom de Vries [this message]
2024-05-03 20:19 ` [PATCH 1/7] [gdb/testsuite] Factor out proc get_portnum Tom Tromey

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=9cdcd951-fc44-48fd-afb7-f9445c1b67da@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --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).