aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2022-12-13 15:59:39 -0700
committerTom Tromey <tom@tromey.com>2023-01-13 13:18:54 -0700
commitfc5ab4bc44e77fbc5aee61d46e8b6f23bef8b371 (patch)
tree2bb0c70eeece6da996b76096694f2303d897fe0d /gdb
parent793862d2f427bdc7b80da5bb917acccb06c4ba61 (diff)
downloadfsf-binutils-gdb-fc5ab4bc44e77fbc5aee61d46e8b6f23bef8b371.zip
fsf-binutils-gdb-fc5ab4bc44e77fbc5aee61d46e8b6f23bef8b371.tar.gz
fsf-binutils-gdb-fc5ab4bc44e77fbc5aee61d46e8b6f23bef8b371.tar.bz2
Use unsupported in 'require'
This changes 'require' to use 'unsupported' rather than 'untested'. The latter doesn't really seem to be correct according to the DejaGNU documentation: Declares a test was not run. `untested' writes in the log file a message beginning with _UNTESTED_, appending the `message' argument. For example, you might use this in a dummy test whose only role is to record that a test does not yet exist for some feature. The example there, and some text elsewhere, is what makes me think this isn't a great fit. On the other hand, 'unsupported' says: Declares that a test case depends on some facility that does not exist in the testing environment.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/lib/gdb.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 88dfdaf..3d416f9 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -9081,7 +9081,7 @@ proc require { args } {
set fn $arg
}
if {$ok != !![uplevel 1 $fn]} {
- untested "require failed: $arg"
+ unsupported "require failed: $arg"
return -code return 0
}
}