From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [dynamic debug] - Check interface and functionality
Date: Thu, 24 Aug 2017 11:55:59 +0200 [thread overview]
Message-ID: <20170824095559.GB28956@rei.lan> (raw)
In-Reply-To: <2042543057.655418.1503511658187.JavaMail.zimbra@redhat.com>
Hi!
> I'm not convinced using EXPECT_* would be the same since I only want
> to report failures and these functions report both TPASS and TFAIL.
> On my machine, this setup produces additional 16k of not that useful
> lines (if something fails, you are still notified about it and know
> every line before it passed). Of course if you can think of a use case
> where having reports for every passed line would make sense I can do
> this change.
Right, haven't thought of that, yes adding 16k of useless output is not
something we want to do.
We may as well add EXPECT_PASS_SILENT or keep the code as it is...
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-08-24 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 10:22 [LTP] [PATCH] [dynamic debug] - Check interface and functionality vkabatov
2017-08-22 13:09 ` Cyril Hrubis
2017-08-23 18:07 ` Veronika Kabatova
2017-08-24 9:55 ` Cyril Hrubis [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=20170824095559.GB28956@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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