aboutsummaryrefslogtreecommitdiff
path: root/opcodes/dis-buf.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2016-01-18 13:54:04 -0500
committerSimon Marchi <simon.marchi@ericsson.com>2016-01-19 10:45:58 -0500
commit10eadbcc2866f11bd93ef379c76524521abdc218 (patch)
treee624af3bfcd28e71a41121da0b6fd28edbe7457d /opcodes/dis-buf.c
parentbef95aacb8501edb086381b3d413485d732f00f3 (diff)
downloadfsf-binutils-gdb-10eadbcc2866f11bd93ef379c76524521abdc218.zip
fsf-binutils-gdb-10eadbcc2866f11bd93ef379c76524521abdc218.tar.gz
fsf-binutils-gdb-10eadbcc2866f11bd93ef379c76524521abdc218.tar.bz2
testsuite: Add --status to runtest invocation
By default, if a test driver (a test .exp) ends with an uncaught error/exception, the runtest command will still have a return code of 0 (success). However, if a test (or the environment) is broken and does not work properly, it should be considered as failed so that we can notice it and fix it. Passing the --status flag to runtest will make it return an error if one of the test it runs ends up with an uncaught error. gdb/testsuite/ChangeLog: * Makefile.in (check-single): Pass --status to runtest. (check/%.exp): Likewise.
Diffstat (limited to 'opcodes/dis-buf.c')
0 files changed, 0 insertions, 0 deletions