All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-raid@vger.kernel.org, jes@trained-monkey.org,
	pmenzel@molgen.mpg.de, logang@deltatee.com, song@kernel.org,
	yukuai3@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH tests 3/5] tests: support to skip checking dmesg
Date: Wed, 24 May 2023 10:40:04 +0200	[thread overview]
Message-ID: <20230524104004.000031bf@linux.intel.com> (raw)
In-Reply-To: <20230523133900.3149123-4-yukuai1@huaweicloud.com>

On Tue, 23 May 2023 21:38:58 +0800
Yu Kuai <yukuai1@huaweicloud.com> wrote:

> From: Yu Kuai <yukuai3@huawei.com>
> 
> Prepare to add a regression test for raid10 that require error injection
> to trigger error path, and kernel will complain about io error, checking
> dmesg for error log will make it impossible to pass this test.
> 
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> ---
>  test | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/test b/test
> index 61d9ee83..b244453b 100755
> --- a/test
> +++ b/test
> @@ -107,8 +107,12 @@ do_test() {
>  		echo -ne "$_script... "
>  		if ( set -ex ; . $_script ) &> $targetdir/log
>  		then
> -			dmesg | grep -iq "error\|call trace\|segfault" &&
> -				die "dmesg prints errors when testing
> $_basename!"
> +			if [ -f "${_script}.inject_error" ]; then
> +				echo "dmesg checking is skipped because test
> inject error"

Following the convention, I would say that it is a "negative test' or just
'negative/md_negative' so errors are expected.

Why not just add some sort of "negative" to the test name?

Anyway:
Acked-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>

Thanks,
Mariusz

  reply	other threads:[~2023-05-24  8:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 13:38 [PATCH tests 0/5] tests: add some regression tests Yu Kuai
2023-05-23 13:38 ` [PATCH tests 1/5] tests: add a new test to check if pluged bio is unlimited for raid10 Yu Kuai
2023-05-24  7:53   ` Mariusz Tkaczyk
2023-05-24  8:26     ` Yu Kuai
2023-05-24  9:00       ` Mariusz Tkaczyk
2023-05-24  9:09         ` Yu Kuai
2023-05-23 13:38 ` [PATCH tests 2/5] tests: add a new test for rdev lifetime Yu Kuai
2023-05-24  8:33   ` Mariusz Tkaczyk
2023-05-24  9:05     ` Yu Kuai
2023-05-24 10:38       ` Mariusz Tkaczyk
2023-05-23 13:38 ` [PATCH tests 3/5] tests: support to skip checking dmesg Yu Kuai
2023-05-24  8:40   ` Mariusz Tkaczyk [this message]
2023-05-23 13:38 ` [PATCH tests 4/5] tests: add a regression test for raid10 deadlock Yu Kuai
2023-05-24  8:48   ` Mariusz Tkaczyk
2023-05-24  9:07     ` Yu Kuai
2023-05-23 13:39 ` [PATCH tests 5/5] tests: add a regression test for raid456 deadlock Yu Kuai
2023-05-24  9:09   ` Mariusz Tkaczyk
2023-05-24  7:56 ` [PATCH tests 0/5] tests: add some regression tests Paul Menzel
2023-05-24  9:11   ` Yu Kuai

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=20230524104004.000031bf@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.com \
    /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.