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 testsuite/30528] New: [gdb/testsuite] FAIL: gdb.dwarf2/per-bfd-sharing.exp: couldn't remove files in temporary cache dir Date: Thu, 08 Jun 2023 11:13:59 +0000 [thread overview] Message-ID: <bug-30528-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30528 Bug ID: 30528 Summary: [gdb/testsuite] FAIL: gdb.dwarf2/per-bfd-sharing.exp: couldn't remove files in temporary cache dir Product: gdb Version: 13.1 Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With a gdb 13.1 based package on SLE-11 i586, I run into: ... (gdb) PASS: gdb.dwarf2/per-bfd-sharing.exp: first=readnow: second=readnow: third=readnow: load third: print foo Executing on host: sh -c "rm /tmp/tmp.xQ6KmzbodJ/*.gdb-index" (timeout = 300) builtin_spawn sh -c rm /tmp/tmp.xQ6KmzbodJ/*.gdb-index^M FAIL: gdb.dwarf2/per-bfd-sharing.exp: couldn't remove files in temporary cache dir testcase /usr/src/packages/BUILD/gdb-13.1/gdb/testsuite/gdb.dwarf2/per-bfd-sharing.exp ... I don't understand what has caused this (part of what makes this difficult is that there's no error message). I'm not able to reproduce this. However, I think that this should not be a FAIL. A FAIL is for when GDB does something incorrect, which is not necesarily the case here, so perhaps this should be warning. However, if the failure to remove the file is due to the file not being there in the first place, then that is a GDB error. We just don't explicitly check for it currently. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-06-08 11:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-08 11:13 vries at gcc dot gnu.org [this message] 2023-10-26 6:03 ` [Bug testsuite/30528] " vries at gcc dot gnu.org 2023-10-26 6:41 ` vries at gcc dot gnu.org 2023-10-26 8:33 ` cvs-commit at gcc dot gnu.org 2023-10-26 8:36 ` 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-30528-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).