public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug external/31410] New: [gdb/Linaro CI progression] FAIL: gdb.base/startup-with-shell.exp: startup_with_shell = off; run_args = *.unique-extension: first argument not expanded Date: Sat, 24 Feb 2024 09:04:28 +0000 [thread overview] Message-ID: <bug-31410-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31410 Bug ID: 31410 Summary: [gdb/Linaro CI progression] FAIL: gdb.base/startup-with-shell.exp: startup_with_shell = off; run_args = *.unique-extension: first argument not expanded Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: external Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- The linaro CI consistently reports a progression on test-case gdb.base/startup-with-shell.exp. AFAICU, this happens because: - the FAIL is listed in an xfails.xfail file, and - the FAIL was fixed. I think the FAIL was fixed by: ... commit 52498004a34dfa4bc55fbf791a4ed4e81599a436 Author: Andrew Burgess <aburgess@redhat.com> Date: Wed Jan 17 09:53:16 2024 +0000 gdb/testsuite: handle long filenames in gdb.base/startup-with-shell.exp I got a report of a failure from Linaro's CI testing for the test gdb.base/startup-with-shell.exp. ... Can we update the xfails.xfail file? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-24 9:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-24 9:04 vries at gcc dot gnu.org [this message] 2024-02-24 9:04 ` [Bug external/31410] " vries at gcc dot gnu.org 2024-02-26 13:10 ` maxim.kuvyrkov at gmail dot com 2024-02-26 14:02 ` [Bug testsuite/31410] [gdb/testsuite] " vries at gcc dot gnu.org 2024-02-26 14:14 ` tromey at sourceware dot org 2024-02-26 14:17 ` vries at gcc dot gnu.org 2024-02-26 14:59 ` cvs-commit at gcc dot gnu.org 2024-02-26 15:01 ` vries at gcc dot gnu.org 2024-02-26 15:14 ` thiago.bauermann at linaro dot 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-31410-4717@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).