From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Muhammad Usama Anjum" <usama.anjum@collabora.com>,
"Shuah Khan" <shuah@kernel.org>
Cc: <kernel@collabora.com>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests: tpm2: redirect python unittest logs to stdout
Date: Fri, 02 Aug 2024 01:23:27 +0300 [thread overview]
Message-ID: <D34XDC7E4AQM.1H8PBFSF9VKPM@kernel.org> (raw)
In-Reply-To: <47ea7423-3aae-4bb3-a41f-1fcb5c07e74b@collabora.com>
On Wed Jul 31, 2024 at 4:42 PM EEST, Muhammad Usama Anjum wrote:
> Reminder
>
> On 7/10/24 1:15 PM, Muhammad Usama Anjum wrote:
> > The python unittest module writes all its output to stderr, even when
> > the run is clean. Redirect its output logs to stdout.
> >
> > Cc: Jarkko Sakkinen <jarkko@kernel.org>
> > Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> > ---
> > tools/testing/selftests/tpm2/test_async.sh | 2 +-
> > tools/testing/selftests/tpm2/test_smoke.sh | 2 +-
> > tools/testing/selftests/tpm2/test_space.sh | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/testing/selftests/tpm2/test_async.sh b/tools/testing/selftests/tpm2/test_async.sh
> > index 43bf5bd772fd4..cf5a9c826097b 100755
> > --- a/tools/testing/selftests/tpm2/test_async.sh
> > +++ b/tools/testing/selftests/tpm2/test_async.sh
> > @@ -7,4 +7,4 @@ ksft_skip=4
> > [ -e /dev/tpm0 ] || exit $ksft_skip
> > [ -e /dev/tpmrm0 ] || exit $ksft_skip
> >
> > -python3 -m unittest -v tpm2_tests.AsyncTest
> > +python3 -m unittest -v tpm2_tests.AsyncTest 2>&1
> > diff --git a/tools/testing/selftests/tpm2/test_smoke.sh b/tools/testing/selftests/tpm2/test_smoke.sh
> > index 58af963e5b55a..20fa70f970a9a 100755
> > --- a/tools/testing/selftests/tpm2/test_smoke.sh
> > +++ b/tools/testing/selftests/tpm2/test_smoke.sh
> > @@ -6,4 +6,4 @@ ksft_skip=4
> >
> > [ -e /dev/tpm0 ] || exit $ksft_skip
> >
> > -python3 -m unittest -v tpm2_tests.SmokeTest
> > +python3 -m unittest -v tpm2_tests.SmokeTest 2>&1
> > diff --git a/tools/testing/selftests/tpm2/test_space.sh b/tools/testing/selftests/tpm2/test_space.sh
> > index 04c47b13fe8ac..93894cbc89a80 100755
> > --- a/tools/testing/selftests/tpm2/test_space.sh
> > +++ b/tools/testing/selftests/tpm2/test_space.sh
> > @@ -6,4 +6,4 @@ ksft_skip=4
> >
> > [ -e /dev/tpmrm0 ] || exit $ksft_skip
> >
> > -python3 -m unittest -v tpm2_tests.SpaceTest
> > +python3 -m unittest -v tpm2_tests.SpaceTest 2>&1
I was on holiday for four weeks so thus the latency. And also
mbsync failed on me for sometime:
https://social.kernel.org/notice/AkX1oAnWFMXja3uN84
Anyway, agreeing with the code changes but I think this
categorizes as a bug so please add the fixes tag and send
v2.
BR, Jarkko
prev parent reply other threads:[~2024-08-01 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 8:15 [PATCH] selftests: tpm2: redirect python unittest logs to stdout Muhammad Usama Anjum
2024-07-31 13:42 ` Muhammad Usama Anjum
2024-07-31 17:45 ` Shuah Khan
2024-08-01 22:24 ` Jarkko Sakkinen
2024-08-01 22:58 ` Shuah Khan
2024-08-02 17:46 ` Jarkko Sakkinen
2024-08-01 22:23 ` Jarkko Sakkinen [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=D34XDC7E4AQM.1H8PBFSF9VKPM@kernel.org \
--to=jarkko@kernel.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 \
/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