This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Regression tester confusion
- From: Geoff Keating <geoffk at geoffk dot org>
- To: mark at codesourcery dot com
- Cc: gdb at sources dot redhat dot com, gcc-regression at gcc dot gnu dot org
- Date: Tue, 7 May 2002 12:44:05 -0700
- Subject: Re: Regression tester confusion
- References: <92880000.1020796022@gandalf.codesourcery.com>
- Reply-to: Geoff Keating <geoffk at redhat dot com>
> 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.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>