Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Frederic Riss <frederic.riss@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [resubmit] gdb.base, r*.exp thru w*.exp
Date: Fri, 18 Jun 2010 07:30:00 -0000	[thread overview]
Message-ID: <AANLkTiloCjTXqbUj6m6lOscrZuaX9qBgmz4VblOngKnl@mail.gmail.com> (raw)
In-Reply-To: <4C1ABC69.3050706@vmware.com>

Hi Michael,

On 18 June 2010 02:23, Michael Snyder <msnyder@vmware.com> wrote:
> Hmmm... I don't recall changing most of those.  Are these all new failures?

I didn't look at the failures I was seeing. After Daniel explained the
breakage, I audited of the whole testsuite for patterns that could
cause random breakage and that's what I reported. Among the cases that
I listed, I saw random failures seemingly introduced by your patches
for mi-return.exp, mi-return2.exp and setshow.exp. I suppose a few
others from the list are new, but maybe there are also pre-existing
ones.


  reply	other threads:[~2010-06-18  7:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 21:01 Michael Snyder
2010-05-20 21:07 ` Joel Brobecker
2010-05-20 21:14   ` Michael Snyder
2010-05-20 21:28 ` Jan Kratochvil
2010-05-20 21:46   ` Michael Snyder
2010-05-20 21:47     ` Jan Kratochvil
2010-05-20 21:57       ` Michael Snyder
2010-05-20 22:02         ` Jan Kratochvil
2010-05-20 22:07           ` Michael Snyder
2010-05-20 22:07         ` Joel Brobecker
2010-05-20 22:21           ` Michael Snyder
2010-06-15 15:56 ` Frederic Riss
2010-06-15 16:19   ` Daniel Jacobowitz
2010-06-16  8:12     ` Frederic Riss
2010-06-18  0:23       ` Michael Snyder
2010-06-18  7:30         ` Frederic Riss [this message]
2010-06-15 17:44   ` Michael Snyder

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=AANLkTiloCjTXqbUj6m6lOscrZuaX9qBgmz4VblOngKnl@mail.gmail.com \
    --to=frederic.riss@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    /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