From 18f1cb1fc5355629c74f7615e358e3007f4e3bae Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Mon, 14 Dec 2020 17:05:11 +0100 Subject: [PATCH] [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 PR testsuite/26963 * lib/gdb.exp (run_on_host): Declare test unsupported if spawn fails. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/lib/gdb.exp | 6 +++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 9a20e7ec65a..500d4445098 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-12-14 Tom de Vries + + PR testsuite/26963 + * lib/gdb.exp (run_on_host): Declare test unsupported if spawn fails. + 2020-12-14 Tom de Vries PR testsuite/26962 diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index e413bab93c4..46728bb936d 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -7005,7 +7005,11 @@ proc run_on_host { test program args } { return 0 } else { verbose -log "run_on_host failed: $output" - fail $test + if { $output == "spawn failed" } { + unsupported $test + } else { + fail $test + } return -1 } } -- 2.30.2