* runtest gdb testsuite oddities.
@ 2011-01-11 23:42 Phil Muldoon
2011-01-12 2:26 ` Joel Brobecker
0 siblings, 1 reply; 3+ messages in thread
From: Phil Muldoon @ 2011-01-11 23:42 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: runtest gdb testsuite oddities.
2011-01-11 23:42 runtest gdb testsuite oddities Phil Muldoon
@ 2011-01-12 2:26 ` Joel Brobecker
2011-01-12 12:30 ` Phil Muldoon
0 siblings, 1 reply; 3+ messages in thread
From: Joel Brobecker @ 2011-01-12 2:26 UTC (permalink / raw)
To: Phil Muldoon; +Cc: gdb
> 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.
Each testcase (.exp) is actually part of the same run. When you think
of scripts being executed, they are actually files being sourced.
So what I am thinking happened to you is that, in your normal context,
you first "ran" (in other words: sourced) a gdb.python testcase that
called "load_lib gdb-python.exp", and thus defined the
gdb_py_test_silent_cmd procedure. "Thanks" to that, by the time dejagnu
"ran" py-infthread.exp, tcl/expect could find gdb_py_test_silent_cmd,
even though the "script" is missing a call to load_lib.
--
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: runtest gdb testsuite oddities.
2011-01-12 2:26 ` Joel Brobecker
@ 2011-01-12 12:30 ` Phil Muldoon
0 siblings, 0 replies; 3+ messages in thread
From: Phil Muldoon @ 2011-01-12 12:30 UTC (permalink / raw)
To: Joel Brobecker; +Cc: gdb
Joel Brobecker <brobecker@adacore.com> writes:
>> 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.
>
> Each testcase (.exp) is actually part of the same run. When you think
> of scripts being executed, they are actually files being sourced.
> So what I am thinking happened to you is that, in your normal context,
> you first "ran" (in other words: sourced) a gdb.python testcase that
> called "load_lib gdb-python.exp", and thus defined the
> gdb_py_test_silent_cmd procedure. "Thanks" to that, by the time dejagnu
> "ran" py-infthread.exp, tcl/expect could find gdb_py_test_silent_cmd,
> even though the "script" is missing a call to load_lib.
It also seems to happen with just a plain old "make check" too (I guess
as it equates to runtest $$/*.exp in each directory.) The import being
sourced from a previous test unit sounds bogus. (Not that I know how to
fix it, or even if we can.)
Cheers
Phil
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-01-12 12:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-11 23:42 runtest gdb testsuite oddities Phil Muldoon
2011-01-12 2:26 ` Joel Brobecker
2011-01-12 12:30 ` Phil Muldoon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox