mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linux-kernel@vger.kernel.org
Cc: jbacik@fb.com, linux-kselftest@vger.kernel.org,
	shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests: Fix loss of test output in run_kselftests.sh
Date: Tue, 16 Jan 2018 09:34:54 -0700	[thread overview]
Message-ID: <628da78f-243a-0fec-5a2c-e2be3691ba80@osg.samsung.com> (raw)
In-Reply-To: <20180116061039.16713-1-mpe@ellerman.id.au>

On 01/15/2018 11:10 PM, Michael Ellerman wrote:
> Commit fbcab13d2e25 ("selftests: silence test output by default")
> changed the run_tests logic as well as the logic to generate
> run_kselftests.sh to redirect test output away from the console.
> 
> As discussed on the list and at kernel summit, this is not a desirable
> default as it means in order to debug a failure the console output is
> not sufficient, you also need access to the test machine to get the
> full test logs. Additionally it's impolite to write directly to
> /tmp/$TEST_NAME on shared systems.
> 
> The change to the run_tests logic was reverted in commit
> a323335e62cc ("selftests: lib.mk: print individual test results to
> console by default"), and instead a summary option was added so that
> quiet output could be requested.
> 
> However the change to run_kselftests.sh was left as-is.
> 
> This commit applies the same logic to the run_kselftests.sh code, ie.
> the script now takes a "--summary" option which suppresses the output,
> but shows all output by default.
> 
> Additionally instead of writing to /tmp/$TEST_NAME the output is
> redirected to the directory where the generated test script is
> located.
> 
> Fixes: fbcab13d2e25 ("selftests: silence test output by default")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>  tools/testing/selftests/Makefile | 9 ++++++++-
>  tools/testing/selftests/lib.mk   | 2 +-
>  2 files changed, 9 insertions(+), 2 deletions(-)

Thanks for catching this. Applied to linux-kselftest next

thanks,
-- Shuah

      reply	other threads:[~2018-01-16 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16  6:10 Michael Ellerman
2018-01-16 16:34 ` 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=628da78f-243a-0fec-5a2c-e2be3691ba80@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=jbacik@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    /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

all inboxes | Powered by JetHome®