When running gdb.base/batch-exit-status.exp I noticed that the test name
contains a newline:
...
PASS: gdb.base/batch-exit-status.exp: : No such file or directory\.^M
: No such file or directory\.: [lindex $result 2] == 0
...
Check for this in ::CheckTestNames::check, such that we have a warning:
...
PASS: gdb.base/batch-exit-status.exp: : No such file or directory\.^M
: No such file or directory\.: [lindex $result 2] == 0
WARNING: Newline in test name
...
Tested on x86_64-linux.
return $message
}
+ # Check if MESSAGE is a well-formed test name.
+ proc _check_well_formed_name { message } {
+ if { [regexp \n $message]} {
+ warning "Newline in test name"
+ }
+ }
+
# Check if MESSAGE contains either the source path or the build path.
# This will result in test names that can't easily be compared between
# different runs of GDB.
if [ _check_duplicates $message ] {
clone_output "DUPLICATE: $message"
}
+
+ _check_well_formed_name $message
}
# If COUNT is greater than zero, disply PREFIX followed by COUNT.