diff options
author | Tom de Vries <tdevries@suse.de> | 2024-05-04 10:41:09 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-05-04 10:41:09 +0200 |
commit | c479e964a86984cbf3278845615c04ada8adfb50 (patch) | |
tree | 8ac289492520bc8611f406c913fbbbfac24dad3b /gold | |
parent | e82dca2a57b05a95d45be74cb59046c79c9ed7d3 (diff) | |
download | binutils-c479e964a86984cbf3278845615c04ada8adfb50.zip binutils-c479e964a86984cbf3278845615c04ada8adfb50.tar.gz binutils-c479e964a86984cbf3278845615c04ada8adfb50.tar.bz2 |
[gdb/testsuite] Use unique portnum in parallel testing (check//% case)
Make target check//% is the gdb variant of a similar gcc make target [1].
When running tests using check//%:
...
$ cd build/gdb
$ make check//unix/{-fPIE/-pie,-fno-PIE/-no-pie} -j2 TESTS=gdb.server/*.exp
...
we get:
...
$ cat build/gdb/testsuite.unix.-fPIE.-pie/cache/portnum
2427
$ cat build/gdb/testsuite.unix.-fno-PIE.-no-pie/cache/portnum
2423
...
The problem is that there are two portnum files used in parallel.
Fix this by:
- creating a common lockdir build/gdb/testsuite.lockdir for make target
check//%,
- passing this down to the runtests invocations using variable GDB_LOCK_DIR,
and
- using GDB_LOCK_DIR in lock_dir.
Tested on aarch64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
PR testsuite/31632
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31632
[1] https://gcc.gnu.org/install/test.html
Diffstat (limited to 'gold')
0 files changed, 0 insertions, 0 deletions