From: Doug Evans <xdje42@gmail.com>
To: paul_koning <Paul_Koning@dell.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Unreliable test suites?
Date: Mon, 26 Oct 2015 05:36:00 -0000 [thread overview]
Message-ID: <CAP9bCMTmBe+3xxkHx4CzcdWYZSeReWynAfG1VdCic9vLs985_g@mail.gmail.com> (raw)
In-Reply-To: <86CED23D-95E1-4A1F-B656-EDD2A2244FE7@dell.com>
On Wed, Oct 14, 2015 at 12:58 PM, <Paul_Koning@dell.com> wrote:
> I'm doing some work on gdb and want to run the testsuites to confirm that I didn't mess it up.
>
> The problem is that a number of them seem to be quite unreliable. I've seen test runs where gdb.btrace/step.exp and/or stepi.exp have a pile of failures, but then when I rerun either just those tests, or the whole suite, they pass.
>
> Since I haven't a clue how the reverse execution stuff works, I don't know if this is expected. It seems strange. I also don't know what to do about it if it's not supposed to be like that. For now, I'm just running things a couple of times, and if they pass once, I call it good enough.
Those particular tests don't fail for me, even with check-parallel,
but then it could depend on the target.
OTOH several tests *are* flaky, especially under load.
What I normally do is for the failures,
run just those tests one at a time (to reduce load induced failures).
And do that in the before and after trees.
If they fail in the before tree too, then don't worry about it.
next prev parent reply other threads:[~2015-10-26 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 19:58 Paul_Koning
2015-10-15 6:17 ` Metzger, Markus T
2015-10-26 5:36 ` Doug Evans [this message]
2015-10-26 14:31 ` Paul_Koning
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=CAP9bCMTmBe+3xxkHx4CzcdWYZSeReWynAfG1VdCic9vLs985_g@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@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