| commit | a0a6e110198c4f7fb4b5baa1f8d158ebf225f7e2 | |
| author | Tom de Vries <tdevries@suse.de> | |
| Sat, 4 May 2024 08:41:09 +0000 (4 10:41 +0200) | ||
| committer | Tom de Vries <tdevries@suse.de> | |
| Sat, 4 May 2024 08:41:09 +0000 (4 10:41 +0200) | ||
| tree | c9ee213bf0e277316b75b38981878dd731c63033 | treesnapshot (tar.gz zip) |
| parent | 007a7cb675ff2aa2a5f22fdcacf17553ee4ae427 | commitdiff |
[gdb/testsuite] Move gpu-parallel.lock to cache dir
The lock directory returned by lock_dir is currently $objdir.
It seems possible to leave a stale lock file that blocks progress in a
following run.
Fix this by using a directory that is guaranteed to be initially empty when
using GDB_PARALLEL, like temp or cache.
In gdb/testsuite/README I found:
...
cache in particular is used to share data across invocations of runtest
...
which seems appropriate, so let's use cache for this.
Tested on aarch64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
The lock directory returned by lock_dir is currently $objdir.
It seems possible to leave a stale lock file that blocks progress in a
following run.
Fix this by using a directory that is guaranteed to be initially empty when
using GDB_PARALLEL, like temp or cache.
In gdb/testsuite/README I found:
...
cache in particular is used to share data across invocations of runtest
...
which seems appropriate, so let's use cache for this.
Tested on aarch64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
| gdb/testsuite/lib/gdb-utils.exp | diffblobblamehistory |