How to abort a test?
Joel Brobecker
brobecker@adacore.com
Sun Jan 17 08:27:00 GMT 2016
Hi Simon,
> I feel completely stupid now. Just under the line I pasted in my
> original message, there is this comment:
>
> 1474 if { [catch "uplevel #0 source $test_file_name"] == 1 } {
> 1475 # If we have a Tcl error, propogate the exit status do make
> 1476 # notices the error.
> 1477 global exit_status exit_error
> 1478 # exit error is set by a command line option
> 1479 if { $exit_status == 0 } {
> 1480 set exit_status $exit_error
> 1481 }
>
> After searching where this goes, I saw the --status argument to runtest:
>
> --status
> Set the exit status to fail on Tcl errors.
>
> Turns out we just need to add this to our runtest invocation to make
> it return non-zero when a test driver, as it calls the test .exp's,
> fails. So we just need to add this to our call to runtest (will send
> a patch later). Sometimes it can be worth it to read the man page
> first...
I admit that some of it flying a little over my head... Does it
mean that we will be able to abort a test if we detect a timeout?
This is one of the things I wanted to do, but didn't have a solution
for, so it'd be fantastic if it helped with that!
--
Joel
More information about the Gdb-patches
mailing list