From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/2] fstests: make some tests that use fsstress easier to debug
Date: Wed, 4 Oct 2023 18:36:56 +1030 [thread overview]
Message-ID: <1ce41890-e4f8-43dd-9a1c-23b2b0912349@gmx.com> (raw)
In-Reply-To: <cover.1696333874.git.fdmanana@suse.com>
On 2023/10/3 22:27, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Some tests that use fsstress are harder to debug than necessary because they
> redirect fsstress' stdout to /dev/null instead of $seqres.full. This means we
> have no way of knowing the seed used by fsstress which often helps to trigger
> a bug/failure. More details on the change logs of each patch.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
>
> Filipe Manana (2):
> fstests: redirect fsstress' stdout to $seqres.full instead of /dev/null
> btrfs/192: use append operator to output log replay results to $seqres.full
>
> tests/btrfs/028 | 2 +-
> tests/btrfs/049 | 2 +-
> tests/btrfs/060 | 2 +-
> tests/btrfs/061 | 2 +-
> tests/btrfs/062 | 2 +-
> tests/btrfs/063 | 2 +-
> tests/btrfs/064 | 2 +-
> tests/btrfs/065 | 2 +-
> tests/btrfs/066 | 2 +-
> tests/btrfs/067 | 2 +-
> tests/btrfs/068 | 2 +-
> tests/btrfs/069 | 2 +-
> tests/btrfs/070 | 2 +-
> tests/btrfs/071 | 2 +-
> tests/btrfs/072 | 2 +-
> tests/btrfs/073 | 2 +-
> tests/btrfs/074 | 2 +-
> tests/btrfs/136 | 2 +-
> tests/btrfs/192 | 4 ++--
> tests/btrfs/232 | 2 +-
> tests/btrfs/261 | 2 +-
> tests/btrfs/286 | 2 +-
> tests/ext4/057 | 2 +-
> tests/ext4/307 | 2 +-
> tests/generic/068 | 2 +-
> tests/generic/269 | 2 +-
> tests/generic/409 | 2 +-
> tests/generic/410 | 2 +-
> tests/generic/411 | 2 +-
> tests/generic/589 | 2 +-
> tests/xfs/051 | 2 +-
> tests/xfs/057 | 2 +-
> tests/xfs/297 | 2 +-
> tests/xfs/305 | 2 +-
> tests/xfs/538 | 2 +-
> 35 files changed, 36 insertions(+), 36 deletions(-)
>
prev parent reply other threads:[~2023-10-04 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 11:57 [PATCH 0/2] fstests: make some tests that use fsstress easier to debug fdmanana
2023-10-03 11:57 ` [PATCH 1/2] fstests: redirect fsstress' stdout to $seqres.full instead of /dev/null fdmanana
2023-10-03 15:24 ` Darrick J. Wong
2023-10-03 11:57 ` [PATCH 2/2] btrfs/192: use append operator to output log replay results to $seqres.full fdmanana
2023-10-03 14:06 ` Anand Jain
2023-10-04 8:06 ` Qu Wenruo [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=1ce41890-e4f8-43dd-9a1c-23b2b0912349@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox