This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [pushed 0/2] Fix test-cp-name-parser build

From: Pedro Alves <palves at redhat dot com>
To: Tom Tromey <tom at tromey dot com>
Cc: gdb-patches at sourceware dot org
Date: Tue, 12 Mar 2019 17:23:34 +0000
Subject: Re: [pushed 0/2] Fix test-cp-name-parser build
References: <20190312170327.14109-1-palves@redhat.com> <87k1h43to0.fsf@tromey.com>

On 03/12/2019 05:10 PM, Tom Tromey wrote:
> Pedro> I'm pondering what could we do to avoid these kinds of regressions.
> Pedro> We could make the buildbot always build these utilities too.  Maybe
> Pedro> even better, add some testsuite testcase that smoke-tests
> Pedro> test-cp-name-parser.
> 
> We could migrate this to use the unit test framework and just not have a
> separate executable.
Oh that might be even better, indeed.

I recall using the executable for quick experimentation when I was
working on the wildmatching stuff, but I think hacking in a unit
test for experimentation would have worked well enough too.

Thanks,
Pedro Alves

Follow-Ups:
- Re: [pushed 0/2] Fix test-cp-name-parser build
  - From: Tom Tromey

References:
- [pushed 0/2] Fix test-cp-name-parser build
  - From: Pedro Alves
- Re: [pushed 0/2] Fix test-cp-name-parser build
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]