Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix spurious mi-basics.exp failures
Date: Sat, 06 May 2006 01:52:00 -0000	[thread overview]
Message-ID: <20060506015210.GA12668@nevyn.them.org> (raw)
In-Reply-To: <200605060119.k461JWLU010082@d12av02.megacenter.de.ibm.com>

On Sat, May 06, 2006 at 03:19:32AM +0200, Ulrich Weigand wrote:
> Hello,
> 
> I'm seeing some FAILs in the mi-basics test case.  They're apparently
> caused by the expected output regexps in some of the mi_gdb_test
> statements lacking the 'serial number' the MI output lines start with.
> 
> Most mi_gdb_test statments already contain that number, but the 202,
> 203, and 208 tests don't have it.  Those are exactly the tests that
> fail for me.  Adding the numbers fixes the test.
> 
> Tested on s390-ibm-linux and s390x-ibm-linux.
> OK for mainline?
> 
> 
> ChangeLog:
> 
> 	* gdb.mi/mi-basics.exp: Add missing serial number to 
> 	expected output in some mi_gdb_test statements.
> 	* gdb.mi/mi2-basics.exp: Likewise.

Are you sure you tested these in the same build tree where they were
broken?

I might be misremembering, but when these tests were added, I think I
complained about the regexps: they fail when the srcdir is specified
using a relative path, but succeed with an absolute path, or the other
way round.

203-environment-directory
203^done,source-path="/big/fsf/commit/src/gdb/testsuite/gdb.mi:$cdir:$cwd"
(gdb) 
PASS: gdb.mi/mi-basics.exp: environment-directory empty-string
operation

Then again, my log does seem to match your results... I don't remember
these failing on this machine before.

From my previous system, an old test run passed with the anchors:

202-environment-directory /big/fsf/commit/src/gdb/testsuite/gdb.mi
202^done,source-path="/big/fsf/commit/src/gdb/testsuite/gdb.mi:$cdir:$cwd"
(gdb) 
PASS: gdb.mi/mi-basics.exp: environment-directory arg operation
203-environment-directory
203^done,source-path="/big/fsf/commit/src/gdb/testsuite/gdb.mi:$cdir:$cwd"
(gdb) 
PASS: gdb.mi/mi-basics.exp: environment-directory empty-string operation


From today:
202-environment-directory /space/fsf/commit/src/gdb/testsuite/gdb.mi
202^done,source-path="/space/fsf/commit/src/gdb/testsuite/gdb.mi:$cdir:$cwd"
(gdb)
FAIL: gdb.mi/mi-basics.exp: environment-directory arg operation
203-environment-directory
203^done,source-path="/space/fsf/commit/src/gdb/testsuite/gdb.mi:$cdir:$cwd"
(gdb)
FAIL: gdb.mi/mi-basics.exp: environment-directory empty-string operation


Oh, I bet I know what's happened!  These are the three tests that
failed based on relative srcdirs or something like that.  So when Bob
committed fixes to the MI testsuite which added anchoring to
mi_gdb_test, they probably failed for him both before and after, and
that's how they were missed.

Bob, does that sound reasonable?  If so, the patch is OK, and thanks!


-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-05-06  1:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06  1:19 Ulrich Weigand
2006-05-06  1:28 ` Bob Rossi
2006-05-06  1:52 ` Daniel Jacobowitz [this message]
2006-05-06  2:02   ` Bob Rossi
2006-05-06  4:08     ` Daniel Jacobowitz
2006-05-06 16:57       ` Ulrich Weigand
2006-05-06 19:52         ` Daniel Jacobowitz

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=20060506015210.GA12668@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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