From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Testcase regression (gdb.base/index-cache.exp) on x86_64 (was: Re: [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id)
Date: Tue, 25 Jun 2019 19:06:00 -0000 [thread overview]
Message-ID: <87mui5scx1.fsf_-_@redhat.com> (raw)
In-Reply-To: <e3c1ae7a-66e3-f587-8633-1147e7c5cc2b@suse.de> (Tom de Vries's message of "Fri, 21 Jun 2019 18:50:57 +0200")
On Friday, June 21 2019, Tom de Vries wrote:
> Thanks for the review, I've updated the rationale.
>
> I'll commit in a bit unless there are further comments.
Hi Tom,
This has caused a testcase regression on x86_64. It was caught by the
BuildBot:
https://sourceware.org/ml/gdb-testers/2019-q2/msg06515.html
The failures are:
PASS -> FAIL: gdb.base/index-cache.exp: test_cache_enabled_hit: check index-cache stats
PASS -> FAIL: gdb.base/index-cache.exp: test_cache_enabled_miss: at least one file was created
PASS -> FAIL: gdb.base/index-cache.exp: test_cache_enabled_miss: check index-cache stats
PASS -> FAIL: gdb.base/index-cache.exp: test_cache_enabled_miss: expected file is there
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-06-25 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:27 [PATCH][gdb/testsuite] Compile index-cache.c with -Wl,--build-id Tom de Vries
2019-06-21 15:47 ` Pedro Alves
2019-06-21 15:53 ` Simon Marchi
2019-06-21 15:54 ` Tom de Vries
2019-06-21 16:32 ` Pedro Alves
2019-06-21 16:51 ` Tom de Vries
2019-06-21 16:51 ` Tom de Vries
2019-06-25 19:06 ` Sergio Durigan Junior [this message]
2019-06-26 3:55 ` [committed][gdb/testsuite] Add back missing debug for index-cache.exp Tom de Vries
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=87mui5scx1.fsf_-_@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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