This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] gdb/testsuite: Don't attempt tests if they fail to compile
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Andrew Burgess <andrew dot burgess at embecosm dot com>, <gdb-patches at sourceware dot org>
- Date: Thu, 11 Jan 2018 17:03:51 -0500
- Subject: Re: [PATCH] gdb/testsuite: Don't attempt tests if they fail to compile
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=simon dot marchi at ericsson dot com;
- References: <20180111190055.4875-1-andrew.burgess@embecosm.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 2018-01-11 02:00 PM, Andrew Burgess wrote:
> In the gdb.base/whatis-ptype-typedefs.exp test, if the test program
> fails to compile, don't run the tests.
Hi Andrew,
That would make the test similar to other test, in that if we fail to
build the test program it's not a failure (it shows as UNTESTED, doesn't
make the test run fail). I find it's a strange behavior though. If a
test program starts not building for some reason, I'd certainly like to
know (e.g. it could be UNRESOLVED), instead of it silently failing.
Any other opinion?
Simon