From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2] selftests: x86: conform test to TAP format output
Date: Thu, 11 Jul 2024 11:52:50 +0500 [thread overview]
Message-ID: <0b731ef9-3110-44d8-b768-ccbf7585a08d@collabora.com> (raw)
In-Reply-To: <0333bafc-295a-4fd8-8099-8fa8c6b0ae23@linuxfoundation.org>
On 7/10/24 9:16 PM, Shuah Khan wrote:
> On 7/10/24 03:37, Muhammad Usama Anjum wrote:
>> This patch brings just readability implements by using kselftests wrappers
>> instead of manual pass/fail test cases counting. It has been on mailing
>> list from several months now. Please can someone ack or nack?
>>
>
> Okay. I think I responded to your other patches that are adding TAP
> to individual tests when kselftest wrapped does it for you based on
> return values.
The current test doesn't return any exit value (hence implicitly always 0
is returned). The return value in addition to some other changes is getting
fixed in this patch.
>
> The reason I don't want to take this patch is if you run the test
> using the recommended method:
>
> make -C tools/testing/selftests/vDSO/ run_tests you will get the
> TAP output because lib.mk runtests framework takes care of this.
This patch is required to correctly return the value so that runtests
fraework can correctly mark the result of the test.
>
> or
>
> make kselftest TARGETS=vDSO will do the same.
>
> Please don't send TAP conversions for individual runs. You will
> start seeing duplicate TAP output which will make it unreadable.
>
> Run the test using make -C or make kselftest TARGETS before
> investing time to concert to TAP. I am not going to take TAP
> conversions patches if make -C or make kselftest TARGETS
> shows TAP.
>
> thanks,
> -- Shuah
>
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-07-11 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:18 [PATCH v2] selftests: x86: conform test to TAP format output Muhammad Usama Anjum
2024-05-28 5:05 ` Muhammad Usama Anjum
2024-07-01 8:38 ` Muhammad Usama Anjum
2024-07-10 9:37 ` Muhammad Usama Anjum
2024-07-10 16:16 ` Shuah Khan
2024-07-11 6:52 ` Muhammad Usama Anjum [this message]
2024-07-11 16:39 ` Shuah Khan
2024-07-12 7:28 ` Muhammad Usama Anjum
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=0b731ef9-3110-44d8-b768-ccbf7585a08d@collabora.com \
--to=usama.anjum@collabora.com \
--cc=binbin.wu@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kernel@collabora.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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