diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2015-09-30 10:04:17 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-09-30 10:04:33 -0400 |
| commit | e019fd1d143061c703691b862f1e282be57b2983 (patch) | |
| tree | 816d11dac7036d5dad4e9f7bd8198a69e0b08ce0 /gdb/ada-tasks.c | |
| parent | 51c935fa4adebc59d41a7868917c2ba78735f58e (diff) | |
| download | gdb-e019fd1d143061c703691b862f1e282be57b2983.zip gdb-e019fd1d143061c703691b862f1e282be57b2983.tar.gz gdb-e019fd1d143061c703691b862f1e282be57b2983.tar.bz2 | |
py-type.exp: Do not run tests if binary fails to build
I noticed this while working on the test case. I believe it would make
sense to skip running the tests if the binary failed to build. Although
I would understand the opposite argument: if the binary does not build
for some reason, we probably want to know about it, and some catastrophic
failures in the tests might alarm us better than a timid "UNTESTED".
gdb/testsuite/ChangeLog:
* gdb.python/py-type.exp: Do not run tests if binaries fail to
build.
Diffstat (limited to 'gdb/ada-tasks.c')
0 files changed, 0 insertions, 0 deletions