From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] fsx-linux: Reduce log output
Date: Thu, 7 Dec 2023 13:44:47 +0100 [thread overview]
Message-ID: <ZXG-P2wOLjrt24Ie@rei> (raw)
In-Reply-To: <6bee08e7-e57f-4d0f-b1a7-3c5441454d9f@suse.com>
Hi!
> > The difference is that TERRNO is applicable to all other types such as
> > TPASS, TFAIL, TBROK, TWARN. This does not make sense for TVERB, you
> > probably do not want to hide passed messages and you certainly do not
> > want to hide falures, bereakages and warnings...
> >
> I was thinking more about TWARN and TINFO.
I'm not sure that we would want to add lesser warnings, i.e. TWARN |
TVERB. We use TWARN mostly in cases where cleanup failed in test
cleanup() and possibly the OS is in an inconsistent state. Also TWARN is
used in places where we would have used TBROK but the test is somehow
able to continue at least partially. I do not think that I have a use
for TWARN | TVERB.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-12-07 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 11:12 [LTP] [PATCH 1/1] fsx-linux: Reduce log output Petr Vorel
2023-12-07 11:18 ` Petr Vorel
2023-12-07 11:22 ` Cyril Hrubis
2023-12-07 11:23 ` Petr Vorel
2023-12-07 12:18 ` Andrea Cervesato via ltp
2023-12-07 12:25 ` Cyril Hrubis
2023-12-07 12:30 ` Andrea Cervesato via ltp
2023-12-07 12:32 ` Cyril Hrubis
2023-12-07 12:34 ` Andrea Cervesato via ltp
2023-12-07 12:39 ` Cyril Hrubis
2023-12-07 12:40 ` Andrea Cervesato via ltp
2023-12-07 12:44 ` Cyril Hrubis [this message]
2023-12-07 12:46 ` Andrea Cervesato via ltp
2023-12-07 12:49 ` Cyril Hrubis
2023-12-07 12:42 ` Petr Vorel
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=ZXG-P2wOLjrt24Ie@rei \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--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