public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>, Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] include: Better documentation for TFAIL and TBROK\
Date: Tue, 15 Oct 2024 18:19:50 +0200	[thread overview]
Message-ID: <20241015161950.GA35679@pevik> (raw)
In-Reply-To: <2748318.lGaqSPkdTl@localhost>

Hi Cyril, Avinesh,

nit: there is trailing "\" in the test subject.

> Hi Cyril,

> On Friday, September 27, 2024 12:18:13 PM GMT+2 Cyril Hrubis wrote:
> > Fixes: #1162

> > Signed-off-by: Cyril Hrubis <chrubis@suse.cz>

> Reviewed-by: Avinesh Kumar <akumar@suse.de>

> Thank you,
> Avinesh

> > ---
> >  include/tst_res_flags.h | 23 +++++++++++++++++++----
> >  1 file changed, 19 insertions(+), 4 deletions(-)

> > diff --git a/include/tst_res_flags.h b/include/tst_res_flags.h
> > index 806940e0d..a79428fa2 100644
> > --- a/include/tst_res_flags.h
> > +++ b/include/tst_res_flags.h
> > @@ -9,11 +9,26 @@
> >  /**
> >   * enum tst_res_flags - Test result reporting flags.
> >   *
> > - * @TPASS: Reports a single success.
> > - * @TFAIL: Reports a single failure.
> > - * @TBROK: Reports a single breakage.
> > + * @TPASS: Reports a single success. Successes increment passed counter and
> > + *         show up in the test results.
> > + *
> > + * @TFAIL: Reports a single failure. Failures increment failure counter and
> > + *         show up in the test results. A failure occurs when test assertion
> > + *         is broken.
> > + *
> > + * @TBROK: Reports a single breakage. Breakages increment breakage counter and
> > + *         show up in the test results. Breakages are reported in cases where a
> > + *         test couldn't be executed due to an unexpected failure when we were
nit: maybe use passive form? "when we were setting the test environment" =>
"during the test setup" or "during setting the test environment"?

> > + *         setting the test environment. The TBROK status is mostly used
> > + *         with tst_brk() which exit the test immediatelly. The difference
> s/immediatelly/immediately 

+1

> > + *         between TBROK and TCONF is that TCONF is used in cases where
> > + *         optional functionality is missing while TBROK is used in cases where
> > + *         something that is supposed to work is broken unexpectedly.
nit (not really sure): "that" => "which"

> > + *
> >   * @TWARN: Reports a single warning. Warnings increment a warning counter and
> > - *         show up in test results.
> > + *         show up in test results. Warnings are somewhere in the middle between
> > + *         TBROK and TCONF. Warnings usually appear when something that is
nit (not really sure): "that" => "which"

Reviewed-by: Petr Vorel <pvorel@suse.cz>

Kind regards,
Petr

> > + *         supposed to be working is broken but the test can somehow continue.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-10-15 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 10:18 [LTP] [PATCH] include: Better documentation for TFAIL and TBROK\ Cyril Hrubis
2024-09-27 11:39 ` Avinesh Kumar
2024-10-15 16:19   ` Petr Vorel [this message]
2024-11-01  9:04     ` Wei Gao via ltp
2024-11-01  9:33     ` Cyril Hrubis

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=20241015161950.GA35679@pevik \
    --to=pvorel@suse.cz \
    --cc=akumar@suse.de \
    --cc=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