Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] kselftests: add per_test_log support
Date: Mon, 11 Dec 2023 18:12:27 +0800	[thread overview]
Message-ID: <ZXbgiwZXt2PVN81e@Laptop-X1> (raw)
In-Reply-To: <ZV6wziKnIs2jZfa2@Laptop-X1>

Ping Shuah. Is there any update I need?

Thanks
Hangbin
On Thu, Nov 23, 2023 at 09:54:26AM +0800, Hangbin Liu wrote:
> Hi Shuah,
> 
> Any comments for this?
> 
> Thanks
> Hangbin
> On Thu, Nov 02, 2023 at 03:50:17PM +0800, Hangbin Liu wrote:
> > By default, all the test output will be printed to stdout or output.log if
> > -s supplied. The kselftest/runner.sh also supports per test log if the
> > variable per_test_logging is set. So add new option -p to set this
> > veriable. Note the -p option is conflict with -s option.
> > 
> > Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> > ---
> >  tools/testing/selftests/run_kselftest.sh | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/testing/selftests/run_kselftest.sh b/tools/testing/selftests/run_kselftest.sh
> > index 92743980e553..965220a314ce 100755
> > --- a/tools/testing/selftests/run_kselftest.sh
> > +++ b/tools/testing/selftests/run_kselftest.sh
> > @@ -20,7 +20,8 @@ usage()
> >  {
> >  	cat <<EOF
> >  Usage: $0 [OPTIONS]
> > -  -s | --summary		Print summary with detailed log in output.log
> > +  -s | --summary		Print summary with detailed log in output.log (conflict with -p)
> > +  -p | --per_test_log		Print test log in /tmp with each test name (conflict with -s)
> >    -t | --test COLLECTION:TEST	Run TEST from COLLECTION
> >    -c | --collection COLLECTION	Run all tests from COLLECTION
> >    -l | --list			List the available collection:test entries
> > @@ -41,6 +42,9 @@ while true; do
> >  			logfile="$BASE_DIR"/output.log
> >  			cat /dev/null > $logfile
> >  			shift ;;
> > +		-p | --per_test_log)
> > +			per_test_logging=1
> > +			shift ;;
> >  		-t | --test)
> >  			TESTS="$TESTS $2"
> >  			shift 2 ;;
> > -- 
> > 2.41.0
> > 

      reply	other threads:[~2023-12-11 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  7:50 [PATCH] kselftests: add per_test_log support Hangbin Liu
2023-11-23  1:54 ` Hangbin Liu
2023-12-11 10:12   ` Hangbin Liu [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=ZXbgiwZXt2PVN81e@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kselftest@vger.kernel.org \
    --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