From: Shuah Khan <skhan@linuxfoundation.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel@collabora.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 0/4] kselftests: vdso: conform tests to TAP output
Date: Tue, 11 Jun 2024 14:37:47 -0600 [thread overview]
Message-ID: <b3741c08-5cc2-4b82-be26-7c2a0f79fa86@linuxfoundation.org> (raw)
In-Reply-To: <20240610054129.1527389-1-usama.anjum@collabora.com>
On 6/9/24 23:41, Muhammad Usama Anjum wrote:
> Conform individual tests to TAP output. One patch conform one test. With
> this series, all vDSO tests become TAP conformant.
>
> First patch conform the test by using kselftest_harness.h. Other patches
> are conforming using default kselftest.h helpers.
>
> All tests have been tested multiple times before and after these
> patches. They are working correctly and outputting TAP messaging to find
> failures quikly when they happen.
> ---
> Changes since v1:
> - Update cover letter
> - Update commit message of first patch
>
> Muhammad Usama Anjum (4):
> kselftests: vdso: vdso_test_clock_getres: conform test to TAP output
> kselftests: vdso: vdso_test_correctness: conform test to TAP output
> kselftests: vdso: vdso_test_getcpu: conform test to TAP output
> kselftests: vdso: vdso_test_gettimeofday: conform test to TAP output
>
> .../selftests/vDSO/vdso_test_clock_getres.c | 68 ++++----
> .../selftests/vDSO/vdso_test_correctness.c | 146 +++++++++---------
> .../testing/selftests/vDSO/vdso_test_getcpu.c | 16 +-
> .../selftests/vDSO/vdso_test_gettimeofday.c | 23 +--
> 4 files changed, 126 insertions(+), 127 deletions(-)
>
I see two changes:
- concvering this test to use kselftes_harness. I am not seeing a value to this.
- Second converting every single print to TAP. This isn't necessary since the
kselftest wrapper prints appropriate summary message based on the KSFT_ code
I want to output before and after to assess the value of this change. TAP conversions
make sense if and when they add value.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-06-11 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 5:41 [PATCH v2 0/4] kselftests: vdso: conform tests to TAP output Muhammad Usama Anjum
2024-06-10 5:41 ` [PATCH v2 1/4] kselftests: vdso: vdso_test_clock_getres: conform test " Muhammad Usama Anjum
2024-06-11 20:32 ` Shuah Khan
2024-06-12 8:17 ` Muhammad Usama Anjum
2024-07-02 10:16 ` Muhammad Usama Anjum
2024-07-09 23:15 ` Shuah Khan
2024-06-10 5:41 ` [PATCH v2 2/4] kselftests: vdso: vdso_test_correctness: " Muhammad Usama Anjum
2024-06-10 5:41 ` [PATCH v2 3/4] kselftests: vdso: vdso_test_getcpu: " Muhammad Usama Anjum
2024-06-10 5:41 ` [PATCH v2 4/4] kselftests: vdso: vdso_test_gettimeofday: " Muhammad Usama Anjum
2024-06-11 20:37 ` Shuah Khan [this message]
2024-06-12 8:22 ` [PATCH v2 0/4] kselftests: vdso: conform tests " 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=b3741c08-5cc2-4b82-be26-7c2a0f79fa86@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=vincenzo.frascino@arm.com \
--cc=yangtiezhu@loongson.cn \
/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