From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb@sourceware.org
Subject: runtest gdb testsuite oddities.
Date: Tue, 11 Jan 2011 23:42:00 -0000 [thread overview]
Message-ID: <m31v4jrosh.fsf@redhat.com> (raw)
Toms check-in today regarding the failure in py-infthread.exp had me
exploring why I did not see it. For some reason when one runs: runtest
gdb.python/*.exp the testsuite seems to pass just fine. But when one
runs just one (failing) exp file, the test fails as it should. I'm not
sure why, and my fu regarding dejagnu is very slim. Can anyone explain
what is going on here? Hopefully it is something silly I have done.
For reference, x8664 running Fedora 14.
Cheers,
Phil
--
Attached log:
[pmuldoon@localhost testsuite]$ runtest gdb.python/*.exp
WARNING: Couldn't find the global config file.
Test Run By pmuldoon on Tue Jan 11 22:03:49 2011
Native configuration is x86_64-unknown-linux-gnu
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../gdb/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running ../../../gdb/gdb/testsuite/gdb.python/py-template.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-mi.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-cmd.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-block.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-infthread.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-type.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-prettyprint.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-frame.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-error.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-function.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-shared.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-pp-maint.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-parameter.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-value.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-section-script.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/lib-types.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-inferior.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-symtab.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/python.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-symbol.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-breakpoint.exp ...
Running ../../../gdb/gdb/testsuite/gdb.python/py-progspace.exp ...
=== gdb Summary ===
# of expected passes 851
# of known failures 1
/home/pmuldoon/git/test_py/obj/gdb/testsuite/../../gdb/gdb version 7.2.50.20110111-cvs -nw -nx -data-directory /home/pmuldoon/git/test_py/obj/gdb/testsuite/../data-directory
[pmuldoon@localhost testsuite]$ runtest gdb.python/py-infthread.exp
WARNING: Couldn't find the global config file.
Test Run By pmuldoon on Tue Jan 11 22:04:16 2011
Native configuration is x86_64-unknown-linux-gnu
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../gdb/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running ../../../gdb/gdb/testsuite/gdb.python/py-infthread.exp ...
ERROR: (DejaGnu) proc "gdb_py_test_silent_cmd {python t0 = gdb.selected_thread ()} {test gdb.selected_thread} 1" does not exist.
The error code is NONE
The info on the error is:
close: spawn id exp5 not open
while executing
"close -i exp5"
invoked from within
"catch "close -i $spawn_id""
=== gdb Summary ===
/home/pmuldoon/git/test_py/obj/gdb/testsuite/../../gdb/gdb version 7.2.50.20110111-cvs -nw -nx -data-directory /home/pmuldoon/git/test_py/obj/gdb/testsuite/../data-directory
next reply other threads:[~2011-01-11 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 23:42 Phil Muldoon [this message]
2011-01-12 2:26 ` Joel Brobecker
2011-01-12 12:30 ` Phil Muldoon
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=m31v4jrosh.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb@sourceware.org \
/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