From: Yu Kuai <yukuai1@huaweicloud.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"nbd@other.debian.org" <nbd@other.debian.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: blktests failures with v6.12 kernel
Date: Fri, 29 Nov 2024 16:37:05 +0800 [thread overview]
Message-ID: <aef69ffa-e556-7eeb-4344-351c66266ee4@huaweicloud.com> (raw)
In-Reply-To: <6crydkodszx5vq4ieox3jjpwkxtu7mhbohypy24awlo5w7f4k6@to3dcng24rd4>
Hi,
在 2024/11/26 10:19, Shinichiro Kawasaki 写道:
> #5: throtl/001 (CKI project, s390 arch)
>
> Recently, CKI project added a configuration to run the blktests thortl group,
> and failures have been repeatedly observed for s390 architecture [7]. I
> suspect the failure message below implies that system performance may affect
> the test result. Further debug is needed.
>
> throtl/001 (basic functionality) [failed]
> runtime ... 6.309s
> --- tests/throtl/001.out 2024-11-23 20:53:13.446546653 +0000
> +++ /mnt/tests/s3.amazonaws.com/arr-cki-prod-lookaside/lookaside/kernel-tests-public/kernel-tests-production.zip/storage/blktests/throtl/blktests/results/nodev/throtl/001.out.bad 2024-11-23 20:53:21.332699696 +0000
> @@ -1,6 +1,6 @@
> Running throtl/001
> +2
> 1
> -1
> -1
> +2
> 1
Perhaps can we have a quick try, and check if issuing IO to a null_blk
in this platform, the latency can't be ignored in seconds.
Thanks,
Kuai
prev parent reply other threads:[~2024-11-29 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 2:19 blktests failures with v6.12 kernel Shinichiro Kawasaki
2024-11-29 7:55 ` Nilay Shroff
2024-11-29 8:37 ` Yu Kuai [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=aef69ffa-e556-7eeb-4344-351c66266ee4@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox