From: Phil Sutter <phil@nwl.cc>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"Yoann P." <yoann.p.public@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] testsuite: ss: Fix spacing in expected output for ssfilter.t
Date: Sat, 10 Nov 2018 22:48:44 +0100 [thread overview]
Message-ID: <20181110214844.GL6440@orbyte.nwl.cc> (raw)
In-Reply-To: <d50e870d746ecb30f1ace3af40db2a249da6b4c2.1541841383.git.sbrivio@redhat.com>
Hi Stefano,
On Sat, Nov 10, 2018 at 10:21:59AM +0100, Stefano Brivio wrote:
> Since commit 00240899ec0b ("ss: Actually print left delimiter for
> columns") changes spacing in ss output, we also need to adjust for that in
> the ss filter test.
>
> Fixes: 00240899ec0b ("ss: Actually print left delimiter for columns")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> testsuite/tests/ss/ssfilter.t | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/testsuite/tests/ss/ssfilter.t b/testsuite/tests/ss/ssfilter.t
> index e74f1765cb72..3091054f2892 100755
> --- a/testsuite/tests/ss/ssfilter.t
> +++ b/testsuite/tests/ss/ssfilter.t
> @@ -12,37 +12,37 @@ export TCPDIAG_FILE="$(dirname $0)/ss1.dump"
> ts_log "[Testing ssfilter]"
>
> ts_ss "$0" "Match dport = 22" -Htna dport = 22
> -test_on "ESTAB 0 0 10.0.0.1:36266 10.0.0.1:22"
> +test_on "ESTAB 0 0 10.0.0.1:36266 10.0.0.1:22"
How about using a regular expression ('test_on' calls grep with '-E')?
E.g. this instead of the above:
| test_on "ESTAB *0 *0 *10.0.0.1:36266 *10.0.0.1:22"
Note that I didn't test this change, just made sure 'grep -E' recognizes
' *' as expected.
Cheers, Phil
next prev parent reply other threads:[~2018-11-11 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 9:21 [PATCH iproute2] testsuite: ss: Fix spacing in expected output for ssfilter.t Stefano Brivio
2018-11-10 21:48 ` Phil Sutter [this message]
2018-11-11 11:50 ` Stefano Brivio
2018-11-11 12:12 ` Phil Sutter
2018-11-12 16:41 ` Stephen Hemminger
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=20181110214844.GL6440@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=stephen@networkplumber.org \
--cc=yoann.p.public@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.