public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/26110] New: invalid command name in one test-case aborts entire test run
Date: Thu, 11 Jun 2020 10:45:11 +0000 [thread overview]
Message-ID: <bug-26110-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26110
Bug ID: 26110
Summary: invalid command name in one test-case aborts entire
test run
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Say we mistakenly do:
...
diff --git a/gdb/testsuite/gdb.ada/O2_float_param.exp
b/gdb/testsuite/gdb.ada/O2_float_param.exp
index 09ebeec405..87f344b1e8 100644
--- a/gdb/testsuite/gdb.ada/O2_float_param.exp
+++ b/gdb/testsuite/gdb.ada/O2_float_param.exp
@@ -29,3 +29,5 @@ runto "increment"
gdb_test "frame" \
"#0\\s+callee\\.increment \\(val(=val@entry)?=99\\.0,
msg=\\.\\.\\.\\).*"
+
+foobar
...
and try to run the test-suite, we have:
...
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 /data/gdb_versions/devel/src/gdb/testsuite/config/unix.exp as
tool-and-target-specific interface file.
Running /data/gdb_versions/devel/src/gdb/testsuite/gdb.ada/O2_float_param.exp
...
SOURCING: /data/gdb_versions/devel/src/gdb/testsuite/gdb.ada/O2_float_param.exp
ERROR: (DejaGnu) proc "foobar" does not exist.
The error code is TCL LOOKUP COMMAND foobar
The info on the error is:
invalid command name "foobar"
while executing
"::tcl_unknown foobar"
("uplevel" body line 1)
invoked from within
"uplevel 1 ::tcl_unknown $args"
=== gdb Summary ===
# of expected passes 2
/data/gdb_versions/devel/build/gdb/gdb version 10.0.50.20200610-git -nw -nx
-data-directory /data/gdb_versions/devel/build/gdb/testsuite/../data-directory
...
So, the entire subsequent test run is aborted because of a mistake inside a
single test-case.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-11 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 10:45 vries at gcc dot gnu.org [this message]
2020-06-11 10:49 ` [Bug testsuite/26110] " vries at gcc dot gnu.org
2020-06-11 11:23 ` vries at gcc dot gnu.org
2020-06-11 14:35 ` vries at gcc dot gnu.org
2020-06-12 7:13 ` cvs-commit at gcc dot gnu.org
2020-06-12 7:16 ` vries at gcc dot gnu.org
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=bug-26110-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).