From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed 0/2] Fix test-cp-name-parser build
Date: Tue, 12 Mar 2019 17:10:00 -0000 [thread overview]
Message-ID: <87k1h43to0.fsf@tromey.com> (raw)
In-Reply-To: <20190312170327.14109-1-palves@redhat.com> (Pedro Alves's message of "Tue, 12 Mar 2019 17:03:25 +0000")
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.
Tom
next prev parent reply other threads:[~2019-03-12 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:03 Pedro Alves
2019-03-12 17:03 ` [pushed 2/2] Fix test-cp-name-parser build, parser_fprintf undefined Pedro Alves
2019-03-12 17:03 ` [pushed 1/2] Fix test-cp-name-parser build, unused variable Pedro Alves
2019-03-12 17:10 ` Tom Tromey [this message]
2019-03-12 17:23 ` [pushed 0/2] Fix test-cp-name-parser build Pedro Alves
2019-03-12 17:48 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1h43to0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox