From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: testsuite errors on Red Hat 8.0
Date: Wed, 16 Apr 2003 16:21:00 -0000 [thread overview]
Message-ID: <ro165pebegh.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <16029.26746.618459.649488@localhost.redhat.com>
On Wed, 16 Apr 2003 10:28:10 -0400, Elena Zannoni <ezannoni@redhat.com> said:
> Daniel Jacobowitz writes:
>> On Tue, Apr 15, 2003 at 09:06:26PM -0700, David Carlton wrote:
>> > I just updated GDB on my laptop for the first time in a while, and I'm
>> > seeing some new testsuite errors: in gdb.base/completion.exp, I get:
>> >
>> > FAIL: gdb.base/completion.exp: (timeout) complete 'info func mar'
>>
>> I think Elena posted a patch for this one that hasn't been applied yet?
> No I haven't. Can you try it and see if it fixes the fail?
Yeah, it does. (Well, it does after I deleted the files
'completion.exp.patch' and 'completion.exp.orig' that I created in
gdb.base; too bad completion.exp is so sensitive to these things!)
Incidentally, should the test be renamed to
completion 'info func marke'
instead of
completion 'info func mar'
? Or would that just annoy people doing regression testing?
>> > FAIL: gdb.base/completion.exp: (timeout) complete 'set follow-fork-mode'
>>
>> Huh, not seen this one before.
> wonder if this is just a cascade failure because of the timeouts.
It was.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-04-16 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 4:06 David Carlton
2003-04-16 4:11 ` Daniel Jacobowitz
2003-04-16 4:27 ` David Carlton
2003-04-16 13:34 ` Daniel Jacobowitz
2003-04-16 14:21 ` Elena Zannoni
2003-04-16 14:29 ` Daniel Jacobowitz
2003-04-16 14:23 ` Elena Zannoni
2003-04-16 16:21 ` David Carlton [this message]
2003-04-16 19:06 ` Elena Zannoni
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=ro165pebegh.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).