From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] request_key04: Use TFAIL instead of TBROK
Date: Wed, 26 Feb 2020 08:23:42 -0500 (EST) [thread overview]
Message-ID: <1576675558.9115231.1582723422538.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200226124826.GA24080@rei>
----- Original Message -----
> Hi!
> > > In personally, I'd let tst_res() only accept 'TPASS, TFAIL, TINFO, TCONF,
> > > TWARN'.
> > +1. Cyril, Jan?
>
> I guess that it does not make much sense to report TBROK and then
> continue the test. But that all depends on how exactly are these states
> defined. Have we ever wrote them down?
>
> I guess that TPASS and TFAIL are obvious.
>
> TINFO is just additional information.
>
> TCONF is test skipped.
>
> TWARN something went wrong but we decided to continue?
This appears to be mostly used in cleanup() when something goes wrong.
So a failure that's not critical, not related to goal of test,
but still something we want to draw attention to.
>
> TBROK something went wrong and we decided to exit?
We do have following in style-guide.txt:
Use +TBROK+ when an unexpected failure unrelated to the goal of the testcase
occurred, and use +TFAIL+ when an unexpected failure related to the goal of
the testcase occurred.
I agree that tst_res with TBROK doesn't make much sense. I see TBROK as
something we can't recover from and need to end the test. Otherwise
if we want to skip part of test, then TCONF looks more fitting.
next prev parent reply other threads:[~2020-02-26 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 8:42 [LTP] [PATCH 1/1] request_key04: Use TFAIL instead of TBROK Petr Vorel
2020-02-26 9:00 ` Li Wang
2020-02-26 9:18 ` Petr Vorel
2020-02-26 9:50 ` Li Wang
2020-02-26 11:37 ` Petr Vorel
2020-02-26 12:04 ` Xiao Yang
2020-02-26 12:48 ` Cyril Hrubis
2020-02-26 13:23 ` Jan Stancek [this message]
2020-02-26 14:02 ` Petr Vorel
2020-02-26 9:22 ` Jan Stancek
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=1576675558.9115231.1582723422538.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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