Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Gleixner" <tglx@linutronix.de>,
	"Mark Brown" <broonie@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Darren Hart" <dvhart@infradead.org>,
	"Davidlohr Bueso" <dave@stgolabs.net>,
	"André Almeida" <andrealmeid@igalia.com>,
	"Shuah Khan" <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: fuxex: Report a unique test name per run of futex_requeue_pi
Date: Mon, 19 Feb 2024 12:53:40 -0700	[thread overview]
Message-ID: <e2d3807c-96f2-4062-a91e-015a083687d6@linuxfoundation.org> (raw)
In-Reply-To: <87a5nwjvj7.ffs@tglx>

On 2/19/24 08:58, Thomas Gleixner wrote:
> On Tue, Feb 13 2024 at 19:06, Mark Brown wrote:
>> The futex_requeue_pi test program is run a number of times with different
>> options to provide multiple test cases. Currently every time it runs it
>> reports the result with a consistent string, meaning that automated systems
>> parsing the TAP output from a test run have difficulty in distinguishing
>> which test is which.
>>
>> The parameters used for the test are already logged as part of the test
>> output, let's use the same format to roll them into the test name that we
>> use with KTAP so that automated systems can follow the results of the
>> individual cases that get run.
>>
>> Signed-off-by: Mark Brown <broonie@kernel.org>
> 
> Acked-by: Thomas Gleixner <tglx@linutronix.de>

Thank you. I will pick this up for Linux 6.9-rc1

thanks,
-- Shuah



      reply	other threads:[~2024-02-19 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 19:06 [PATCH] selftests: fuxex: Report a unique test name per run of futex_requeue_pi Mark Brown
2024-02-14 21:08 ` Davidlohr Bueso
2024-02-19 15:58 ` Thomas Gleixner
2024-02-19 19:53   ` Shuah Khan [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=e2d3807c-96f2-4062-a91e-015a083687d6@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=andrealmeid@igalia.com \
    --cc=broonie@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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