Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/8] Fix gdb's testsuite test names
Date: Fri, 25 Nov 2016 17:31:00 -0000	[thread overview]
Message-ID: <01dc0b4ef0735c891cb9be0e52151ab9@polymtl.ca> (raw)
In-Reply-To: <1480093744-13771-1-git-send-email-lgustavo@codesourcery.com>

On 2016-11-25 12:08, Luis Machado wrote:
> I was going to go with a single patch for this, but i kept hitting 
> other
> cases where i needed to adjust the regular expressions and substitution 
> rules.
> 
> I then decided to have a series with each individual piece that should 
> make it
> easier to review as well. The changes are all pretty mechanical, but it 
> would
> be nice to have another pair of eyes looking at these to make sure 
> nothing
> incorrect got through.
> 
> The first patch handles the "testfile as test name" problem. The rest 
> of the
> series handles test names starting with uppercase.
> 
> Luis Machado (8):
>   Fixup testcases outputting own name as a test name
>   Fix test names starting with uppercase output by basic functions
>   Fix test names starting with uppercase using gdb_test on a single
>     line.
>   Fix test names starting with uppercase using gdb_test_no_output
>   Fix test names starting with uppercase using gdb_test_multiple
>   Fix test names starting with uppercase using multi-line
>     gdb_test/mi_gdb_test
>   Fix test names starting with uppercase using multi-line
>     gdb_test_no_output
>   Fix test names starting with uppercase using multi-line
>     gdb_test_multiple

Hi Luis,

I'll take a quick look at those.  While applying, git gave me these 
warnings.  It's probably extraneous spaces that were there before, but 
if you feel like it you can remove them.


Applying: Fix test names starting with uppercase output by basic 
functions
.git/rebase-apply/patch:3302: trailing whitespace.
	pass "thread command"
warning: 1 line adds whitespace errors.

Applying: Fix test names starting with uppercase using gdb_test on a 
single line.
.git/rebase-apply/patch:1325: trailing whitespace.
gdb_test "print r" " = -1" "test cos(pi) is equal to -1"
.git/rebase-apply/patch:1477: trailing whitespace.
gdb_test "set print test-enum-param three" "Undefined item: \"three\".*" 
"set invalid enum parameter"
warning: 2 lines add whitespace errors.

Simon


  parent reply	other threads:[~2016-11-25 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 17:09 Luis Machado
2016-11-25 17:09 ` [PATCH 6/8] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test Luis Machado
2016-11-25 17:09 ` [PATCH 5/8] Fix test names starting with uppercase using gdb_test_multiple Luis Machado
2016-11-25 17:09 ` [PATCH 8/8] Fix test names starting with uppercase using multi-line gdb_test_multiple Luis Machado
2016-11-25 17:09 ` [PATCH 1/8] Fixup testcases outputting own name as a test name Luis Machado
2016-11-25 17:28   ` Pedro Alves
2016-11-25 17:37     ` Luis Machado
2016-11-25 17:48       ` Simon Marchi
2016-11-25 17:53         ` Luis Machado
2016-11-25 17:55         ` Pedro Alves
2016-11-25 18:02           ` Simon Marchi
2016-11-25 18:26             ` Luis Machado
2016-11-25 18:39               ` Pedro Alves
2016-11-25 17:09 ` [PATCH 3/8] Fix test names starting with uppercase using gdb_test on a single line Luis Machado
2016-11-25 17:09 ` [PATCH 4/8] Fix test names starting with uppercase using gdb_test_no_output Luis Machado
2016-11-25 17:09 ` [PATCH 7/8] Fix test names starting with uppercase using multi-line gdb_test_no_output Luis Machado
2016-11-25 17:10 ` [PATCH 2/8] Fix test names starting with uppercase output by basic functions Luis Machado
2016-11-25 18:00   ` Pedro Alves
2016-11-25 17:31 ` Simon Marchi [this message]
2016-11-25 17:35   ` [PATCH 0/8] Fix gdb's testsuite test names Luis Machado

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=01dc0b4ef0735c891cb9be0e52151ab9@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.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