From: Daniel Jacobowitz <drow@mvista.com>
To: Geoff Keating <geoffk@redhat.com>
Cc: mark@codesourcery.com, gdb@sources.redhat.com,
gcc-regression@gcc.gnu.org
Subject: Re: Regression tester confusion
Date: Tue, 07 May 2002 13:13:00 -0000 [thread overview]
Message-ID: <20020507201308.GA28662@nevyn.them.org> (raw)
In-Reply-To: <200205071944.g47Ji5V14853@desire.geoffk.org>
On Tue, May 07, 2002 at 12:44:05PM -0700, Geoff Keating wrote:
> > Date: Tue, 07 May 2002 11:27:02 -0700
> > From: Mark Mitchell <mark@codesourcery.com>
> > Content-Disposition: inline
> >
> > I'm confused. The regression tester seems to be saying that I broke
> > mips-elf with my recent checkin to rs6000/sysv4.h, which seems odd.
> >
> > Am I going crazy?
>
> There's something odd going on with mips-elf gdb.base/interrupt.exp.
> It seems to be failing at random---this is the third time it's
> mysteriously appeared. The symptoms have been that the .log file
> contains:
>
> (gdb) PASS: gdb.base/interrupt.exp: call function a second time
> continue
> Continuing.
> PASS: gdb.base/interrupt.exp: continue
> data
>
> data
> FAIL: gdb.base/interrupt.exp: echo data (timeout)
> end of file
>
> The gdb testsuite is looking for the 'data' output, which as you can
> see is there, and so the testcase should pass.
>
> The problem seems to happen only when the machine is under other
> load---specifically, when the machine is trying to update its binutils
> & gdb. I suspect that dejagnu is not properly matching the regexp
> because the extra activity on the machine is causing it to be given
> the output in two or more pieces. The kernel and dejagnu versions on
> the two machines (mips-elf is on anubis with a 2.4 kernel, native &
> powerpc are on maat with 2.2) are different; hopefully, soon the
> dejagnu versions will be synchronized, which should help to narrow
> down the problem.
>
> If anyone's seen this before (especially if you fixed it!),
> I'd be interested to hear about it.
This usually means that the previous DejaGNU command did not explicitly
consume enough input... Although in this case, it looks as if there are
an invalid extra \r\n between the 'data's.
The comment two tests up in interrupt.exp sounds as if there's a known
timing problem here. Did "call function when asleep" fail, causing the
extra newline to get sent?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-07 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <92880000.1020796022@gandalf.codesourcery.com>
2002-05-07 12:44 ` Geoff Keating
2002-05-07 13:13 ` Daniel Jacobowitz [this message]
2002-05-07 15:47 ` Geoff Keating
2002-05-07 14:27 Michael Elizabeth Chastain
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=20020507201308.GA28662@nevyn.them.org \
--to=drow@mvista.com \
--cc=gcc-regression@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=geoffk@redhat.com \
--cc=mark@codesourcery.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