From: Michael Chastain <mec.gnu@mindspring.com>
To: schwab@suse.de, eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] Test Suite: build != host
Date: Fri, 20 Aug 2004 15:07:00 -0000 [thread overview]
Message-ID: <412613D1.nail1XO16AREJ@mindspring.com> (raw)
In-Reply-To: <01c486c5$Blat.v2.2.2$eed2fae0@zahav.net.il>
andreas> IMHO @samp would be the right one.
eli> It depends on what "UNRESOLVED" means, exactly. I must confess I
eli> don't understand what does it mean "return UNRESOLVED". Is it a
eli> literal string printed by the test script, or is it something else?
That's right, it's a literal string.
Here is an excerpt from a gdb.sum file:
Running /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.exp ...
gdb compile failed, /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c: In function `main':
/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:39: warning: incompatible implicit declaration of built-in function 'exit'
/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:47: warning: incompatible implicit declaration of built-in function 'exit'
WARNING: Testcase compile failed, so all tests in this file will automatically fail.
ERROR: (timeout) GDB never initialized after 10 seconds.
WARNING: remote_expect statement without a default case?!
ERROR: couldn't load /tmp/migbat-testgdb-49vpUkli/test/gdb.base/unload into gdb (end of file).
UNRESOLVED: gdb.base/unload.exp: set pending breakpoint
FAIL: gdb.base/unload.exp: single pending breakpoint info
FAIL: gdb.base/unload.exp: running program
FAIL: gdb.base/unload.exp: continuing to end of program
FAIL: gdb.base/unload.exp: rerun to shared library breakpoint
FAIL: gdb.base/unload.exp: continuing to end of program second time
This script, unload.exp, has some WARNING, ERROR, UNRESOLVED,
and FAIL results.
(The actual bug has already been fixed, I'm just grabbing this
excerpt to illustrate UNRESOLVED).
My wording is:
DejaGNU supports separate build, host, and target machines. However,
some @value{GDBN} test scripts do not work if the host machine is
separate from the build machine. These scripts will return an
UNRESOLVED result in such an environment.
I'm open to alternate wording, and I'm definitely open to improving
the markup.
next prev parent reply other threads:[~2004-08-20 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 9:48 Michael Chastain
2004-08-19 9:56 ` Andreas Schwab
2004-08-20 15:00 ` Eli Zaretskii
2004-08-20 15:07 ` Michael Chastain [this message]
2004-08-20 16:34 ` Eli Zaretskii
2004-08-19 13:21 ` Daniel Jacobowitz
2004-08-19 16:07 ` Michael 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=412613D1.nail1XO16AREJ@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
/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