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/30528] [gdb/testsuite] FAIL: gdb.dwarf2/per-bfd-sharing.exp: couldn't remove files in temporary cache dir
Date: Thu, 26 Oct 2023 08:33:49 +0000	[thread overview]
Message-ID: <bug-30528-4717-V6fJB4KwJP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30528-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30528

--- Comment #3 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=743d3f0945c625ce5647130b506eeb6940dfc12e

commit 743d3f0945c625ce5647130b506eeb6940dfc12e
Author: Tom de Vries <tdevries@suse.de>
Date:   Thu Oct 26 10:34:24 2023 +0200

    [gdb/testsuite] Add wait-for-index-cache in gdb.dwarf2/per-bfd-sharing.exp

    If we make writing an index-cache entry very slow by doing this in
    index_cache::store:
    ...
       try
         {
    +      sleep (15);
           index_cache_debug ("writing index cache for objfile %s",
                             bfd_get_filename (per_bfd->obfd));
    ...
    we run into:
    ...
    FAIL: gdb.dwarf2/per-bfd-sharing.exp: \
      couldn't remove files in temporary cache dir
    ...

    The FAIL happens because there is no index-cache entry in the cache dir.

    The problem is that gdb is killed (by gdb_exit) before the index-cache
entry
    is written.

    Fix this by using "maint wait-for-index-cache".

    Tested on x86_64-linux.

    PR testsuite/30528
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30528

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-10-26  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 11:13 [Bug testsuite/30528] New: " vries at gcc dot gnu.org
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 [this message]
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-V6fJB4KwJP@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: link
Be 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).