diff options
author | Tom de Vries <tdevries@suse.de> | 2020-12-14 17:05:11 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2020-12-14 17:05:11 +0100 |
commit | 18f1cb1fc5355629c74f7615e358e3007f4e3bae (patch) | |
tree | 11a0bca4f824b9428dacecd5e956ddab301ffb5c /gdb/testsuite/gdb.trace/pending.c | |
parent | 519155c9f6804988e35c8537c4506e877176c9b1 (diff) | |
download | gdb-18f1cb1fc5355629c74f7615e358e3007f4e3bae.zip gdb-18f1cb1fc5355629c74f7615e358e3007f4e3bae.tar.gz gdb-18f1cb1fc5355629c74f7615e358e3007f4e3bae.tar.bz2 |
[gdb/testsuite] Handle missing xz in gdb.base/gnu-debugdata.exp
When running test-case gdb.base/gnu-debugdata.exp on SLE-11, I run into:
...
FAIL: gdb.base/gnu-debugdata.exp: xz
...
The fact that xz is not installed does not mean there's a fail, merely that
the test is unsupported.
Fix this by detecting the "spawn failed" reply in run_on_host and issuing
UNSUPPORTED instead.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2020-12-14 Tom de Vries <tdevries@suse.de>
PR testsuite/26963
* lib/gdb.exp (run_on_host): Declare test unsupported if spawn fails.
Diffstat (limited to 'gdb/testsuite/gdb.trace/pending.c')
0 files changed, 0 insertions, 0 deletions