linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Ryan Roberts <ryan.roberts@arm.com>, Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>, Peter Xu <peterx@redhat.com>,
	Aishwarya TCV <Aishwarya.TCV@arm.com>, <linux-mm@kvack.org>,
	<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v1] selftests/mm: Log run_vmtests.sh results in TAP format
Date: Fri, 15 Dec 2023 18:40:05 -0800	[thread overview]
Message-ID: <fb91ab59-ab5c-45c4-a413-bd6c060bfcc8@nvidia.com> (raw)
In-Reply-To: <d99367ef-72e0-48ad-ba83-45e25efdf0fc@nvidia.com>

On 12/15/23 18:25, John Hubbard wrote:
> On 12/15/23 06:28, Ryan Roberts wrote:
> ...
>> I've kept all the existing "pretty" output and results summary as is, it just
>> gets a hash in front of it when TAP is enabled.
>>
>> so this:
>>
>> -----------------------
>> running ./hugepage-mmap
>> -----------------------
>> Returned address is 0xffff89e00000
>> First hex is 0
>> First hex is 3020100
>> [PASS]
>> SUMMARY: PASS=1 SKIP=0 FAIL=0
>>
>> becomes this:
>>
>> TAP version 13
>> # -----------------------
>> # running ./hugepage-mmap
>> # -----------------------
>> # Returned address is 0xffff89e00000
>> # First hex is 0
>> # First hex is 3020100
>> # [PASS]
>> ok 1 hugepage-mmap
>> # SUMMARY: PASS=1 SKIP=0 FAIL=0
>> 1..1
>>
>> If you think the latter is ofensive, then I can do the wrapping as you suggest.
> 
> I applied this and ran the tests, all while carefully reminding myself
> to "think like a human". :) And from that perspective, to me, the output
> is effectively the same: the leading '#' characters do not really change
> anything, from a readability point of view.
> 
> So IMHO you're on perfectly solid ground, if you just switch over
> directly to this format.
> 
> Tested-by: John Hubbard <jhubbard@nvidia.com>
> 

I should also point out that some of the subtests already attempt a TAP
output. So now we end up with TAP-within-TAP output for those programs.

For example:
     # -----------------------
     # running ./madv_populate
     # -----------------------
     # TAP version 13
     # 1..21
     # # [RUN] test_prot_read
     # ok 1 MADV_POPULATE_READ with PROT_READ
     # ok 2 MADV_POPULATE_WRITE with PROT_READ
     # # [RUN] test_prot_write
     # ok 3 MADV_POPULATE_READ with PROT_WRITE
     ...etc...

Note the double level of leading '#' characters.

Again, this is still readable enough for humans. But it should probably
be removed in subsequent patches to the subtests.


thanks,
-- 
John Hubbard
NVIDIA



  reply	other threads:[~2023-12-16  2:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 16:24 Ryan Roberts
2023-12-15 13:54 ` Mark Brown
2023-12-15 13:58   ` Ryan Roberts
2023-12-15 14:08     ` Mark Brown
2023-12-15 14:28       ` Ryan Roberts
2023-12-15 14:34         ` Mark Brown
2023-12-16  2:25         ` John Hubbard
2023-12-16  2:40           ` John Hubbard [this message]
2023-12-18 11:32             ` Ryan Roberts
2023-12-19  0:51               ` John Hubbard
2023-12-19  0:55                 ` John Hubbard
2023-12-19  8:33                   ` Ryan Roberts

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=fb91ab59-ab5c-45c4-a413-bd6c060bfcc8@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=Aishwarya.TCV@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.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