From: Josef Bacik <josef@toxicpanda.com>
To: Shuah Khan <shuah@kernel.org>
Cc: josef@toxicpanda.com, Josef Bacik <jbacik@fb.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 3/3] selftests: silence test output by default
Date: Mon, 18 Sep 2017 13:52:56 -0400 [thread overview]
Message-ID: <20170918175254.lsdzqvjm4uvix4rj@destiny> (raw)
In-Reply-To: <e8b067d2-9cef-2f3c-78a5-d6630aa765c1@kernel.org>
On Mon, Sep 18, 2017 at 11:46:18AM -0600, Shuah Khan wrote:
> On 09/18/2017 11:37 AM, josef@toxicpanda.com wrote:
> > From: Josef Bacik <jbacik@fb.com>
> >
> > Some of the networking tests are very noisy and make it impossible to
> > see if we actually passed the tests as they run. Default to suppressing
> > the output from any tests run in order to make it easier to track what
> > failed.
> >
> > Signed-off-by: Josef Bacik <jbacik@fb.com>
> > --
>
> This change suppresses pass/fail wrapper output for all tests, not just the
> networking tests.
>
> Could you please send me before and after results for what you are trying
> to fix.
>
Yeah I wanted to suppress extraneous output from everybody, I just happened to
notice it because I was testing net. The default thing already spits out what
it's running and pass/fail, there's no need to include all of the random output
unless the user wants to go and run the test manually. As it is now it's
_impossible_ to tell what ran and what passed/failed because of all the random
output.
Ideally kselftests would work like xfstests does and simply capture the output
to a log so you could go check afterwards, but that's a lot more work. Making
it easier to tell which tests passed/failed is a good enough first step.
Thanks,
Josef
next prev parent reply other threads:[~2017-09-18 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 17:32 [PATCH 1/3] selftest: add a reuseaddr test josef
2017-09-18 17:32 ` [PATCH 2/3] selftests: actually run the various net selftests josef
2017-09-18 22:14 ` Shuah Khan
2017-09-19 13:34 ` Josef Bacik
2017-09-19 18:14 ` Willem de Bruijn
2017-09-19 20:00 ` Shuah Khan
2017-09-18 17:37 ` [PATCH 3/3] selftests: silence test output by default josef
2017-09-18 17:46 ` Shuah Khan
2017-09-18 17:52 ` Josef Bacik [this message]
2017-09-18 18:13 ` Shuah Khan
2017-09-18 18:24 ` Josef Bacik
2017-09-18 19:48 ` Shuah Khan
2017-09-18 20:19 ` Josef Bacik
2017-09-18 21:36 ` Shuah Khan
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=20170918175254.lsdzqvjm4uvix4rj@destiny \
--to=josef@toxicpanda.com \
--cc=davem@davemloft.net \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.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