From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org
Cc: blktests-ci-bot@kernel.org
Subject: Re: [v3 for-next 0/3] block: delay support for error injection
Date: Wed, 14 Oct 2026 20:57:25 +0900 [thread overview]
Message-ID: <as9tTCdj-BP_88ga@shinmob> (raw)
In-Reply-To: <a99313f8e07b8eef09229050598baf914fea410a5b07ccd515822ebd9ad9fc29@mailrelay.wdc.com>
On Oct 13, 2026 / 20:04, shinichiro.kawasaki@wdc.com wrote:
> Dear patch submitter,
>
> Blktests CI has tested the following submission:
> Status: FAILURE
> Name: [v3,for-next,0/3] block: delay support for error injection
> Patchwork: https://patchwork.kernel.org/series/1175637/&state=*
> Run record: https://github.com/linux-blktests/linux-block/actions/runs/38472940769
>
>
> Failed test cases: loop/006
Please ignore this failure report. The loop/006 failure is known, and it was
triggered by another commit [*]. Sorry for the noise.
[*] https://lore.kernel.org/linux-block/as8-8rDJmUb1FxbP@shinmob/
prev parent reply other threads:[~2026-10-14 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 22:16 [v3 for-next 0/3] block: delay support for error injection Md Haris Iqbal
2026-09-28 22:16 ` [v3 for-next 1/3] block: Reject unknown status tags in error injection rules Md Haris Iqbal
2026-10-05 8:49 ` Christoph Hellwig
2026-09-28 22:16 ` [v3 for-next 2/3] block: allow error injection rules to delay bios Md Haris Iqbal
2026-10-05 8:56 ` Christoph Hellwig
2026-09-28 22:16 ` [v3 for-next 3/3] Documentation: block: document error injection delay feature Md Haris Iqbal
2026-10-05 8:56 ` Christoph Hellwig
2026-10-14 3:04 ` [v3 for-next 0/3] block: delay support for error injection shinichiro.kawasaki
2026-10-14 11:57 ` Shin'ichiro Kawasaki [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=as9tTCdj-BP_88ga@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=blktests-ci-bot@kernel.org \
--cc=linux-block@vger.kernel.org \
/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.