From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] selftests: mptcp: add time per subtests in TAP output
Date: Wed, 4 Sep 2024 22:41:15 +0200 [thread overview]
Message-ID: <d91e6446-bdb1-4c22-a5c3-4c3f3dccebdb@kernel.org> (raw)
In-Reply-To: <20240904124025.3ec84142@kernel.org>
Hi Jakub,
Thank you for your reply!
On 04/09/2024 21:40, Jakub Kicinski wrote:
> On Wed, 4 Sep 2024 18:15:09 +0200 Matthieu Baerts wrote:
>>> Best I could come up with is:
>>>
>>> diff --git a/contest/remote/vmksft-p.py b/contest/remote/vmksft-p.py
>>> index fe9e87abdb5c..a37245bd5b30 100755
>>> --- a/contest/remote/vmksft-p.py
>>> +++ b/contest/remote/vmksft-p.py
>>> @@ -73,7 +73,7 @@ group3 testV skip
>>> tests = []
>>> nested_tests = False
>>>
>>> - result_re = re.compile(r"(not )?ok (\d+)( -)? ([^#]*[^ ])( # )?([^ ].*)?$")
>>> + result_re = re.compile(r"(not )?ok (\d+)( -)? ([^#]*[^ ])( +# )?([^ ].*)?$")
>>
>> Looks good to me. While at it, we can add a '+' for the spaces after the
>> '#':
>>
>> ( +# +)
>
> 👍️
>
>> I see you didn't commit the previous modification. I can open a PR if it
>> helps.
>
> I was just playing with the regexps in the interpreter. If you could
> send a PR that'd perfect.
Sure, done:
https://github.com/linux-netdev/nipa/pull/38
>>> time_re = re.compile(r"time=(\d+)ms")
>>>
>>> for line in full_run.split('\n'):
>>>
>>> Thoughts?
>>
>> In my v2, I will also strip these trailing whitespaces in the selftests,
>> they don't need to be there.
>
> Up to you - it doesn't violate the KTAP format and the visual alignment
> is nice. But it may trip up more regexps..
Yes, better be safe... I will keep the visual alignment for the non-TAP
output.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-09-04 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 11:13 [PATCH net-next 0/3] selftests: mptcp: add time per subtests in TAP output Matthieu Baerts (NGI0)
2024-09-02 11:13 ` [PATCH net-next 1/3] selftests: mptcp: lib: " Matthieu Baerts (NGI0)
2024-09-02 11:13 ` [PATCH net-next 2/3] sefltests: mptcp: connect: remote time " Matthieu Baerts (NGI0)
2024-09-04 0:13 ` Jakub Kicinski
2024-09-02 11:13 ` [PATCH net-next 3/3] selftests: mptcp: reset the last TS before the first test Matthieu Baerts (NGI0)
2024-09-03 23:22 ` [PATCH net-next 0/3] selftests: mptcp: add time per subtests in TAP output Jakub Kicinski
2024-09-03 23:30 ` Jakub Kicinski
2024-09-04 16:15 ` Matthieu Baerts
2024-09-04 19:40 ` Jakub Kicinski
2024-09-04 20:41 ` Matthieu Baerts [this message]
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=d91e6446-bdb1-4c22-a5c3-4c3f3dccebdb@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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