All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] ustat0{1, 2}: Mark failure on Btrfs with known-fail tag
Date: Tue, 4 Jan 2022 12:02:35 +0100	[thread overview]
Message-ID: <YdQpS0WPRvz4vZup@yuki> (raw)
In-Reply-To: <20220103151332.1989-2-pvorel@suse.cz>

Hi!
> --- a/testcases/kernel/syscalls/ustat/ustat01.c
> +++ b/testcases/kernel/syscalls/ustat/ustat01.c
> @@ -44,6 +44,10 @@ static void setup(void)
>  static struct tst_test test = {
>  	.test_all = run,
>  	.setup = setup,
> +	.tags = (const struct tst_tag[]) {
> +		{"known-fail", "ustat() is known to fail with EINVAL on Btrfs"},
                                   ^
				   Maybe we should just remove the
				   "known to fail" from these messages.

Since the code in the library will print:

---
You _MAY_ be hit by known kernel failures:

ustat() is known to fail with EINVAL on Btrfs
---

so the 'known to fail' part is redundant here.

What about:

---
You _MAY_ be hit by known kernel failures:

ustat() fails with EINVAL on Btrfs
---

Other than this I think that this is a good way how to put these kind of
hints into the testcases.


Also I do wonder if there is a good URL that would contain more verbose
description of the problem but I guess there isn't. Well maybe this one:

https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg95697.html

Not sure how to encode that, maybe just add it to the test top level
comment?

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2022-01-04 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 15:13 [LTP] [PATCH 1/2] lib: Add known-fail test tag Petr Vorel
2022-01-03 15:13 ` [LTP] [PATCH 2/2] ustat0{1, 2}: Mark failure on Btrfs with known-fail tag Petr Vorel
2022-01-04 11:02   ` Cyril Hrubis [this message]
2022-01-05 17:16     ` Petr Vorel
2022-01-14 14:19       ` Cyril Hrubis
2022-01-14 17:58         ` 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=YdQpS0WPRvz4vZup@yuki \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.