public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/26963] FAIL: gdb.base/gnu-debugdata.exp: xz Date: Mon, 14 Dec 2020 16:05:26 +0000 [thread overview] Message-ID: <bug-26963-4717-6NWwpHkfBu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26963-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26963 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=18f1cb1fc5355629c74f7615e358e3007f4e3bae commit 18f1cb1fc5355629c74f7615e358e3007f4e3bae Author: Tom de Vries <tdevries@suse.de> Date: Mon Dec 14 17:05:11 2020 +0100 [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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-14 16:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 14:30 [Bug testsuite/26963] New: " vries at gcc dot gnu.org 2020-12-14 7:43 ` [Bug testsuite/26963] " vries at gcc dot gnu.org 2020-12-14 16:05 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-14 16:07 ` vries at gcc dot gnu.org
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=bug-26963-4717-6NWwpHkfBu@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).