From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] include: Better documentation for TFAIL and TBROK\
Date: Fri, 1 Nov 2024 10:33:51 +0100 [thread overview]
Message-ID: <ZySgf_RyPfZUXCXD@yuki.lan> (raw)
In-Reply-To: <20241015161950.GA35679@pevik>
Hi!
> nit: there is trailing "\" in the test subject.
I know, fixed.
> > > 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"?
That is indeed better, thanks.
> > > + * setting the test environment. The TBROK status is mostly used
> > > + * with tst_brk() which exit the test immediatelly. The difference
> > s/immediatelly/immediately
>
> +1
Fixed as well.
> > > + * 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"
AFAIK both can work here, so I kept the original.
Thanks a lot everyone for the reviews, pushed.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-11-01 9:34 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
2024-11-01 9:04 ` Wei Gao via ltp
2024-11-01 9:33 ` 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=ZySgf_RyPfZUXCXD@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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