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] generic/019: redirect fsstress output to log file instead
Date: Thu, 1 Aug 2024 08:59:25 +0930 [thread overview]
Message-ID: <4bcf1b73-e59f-41fb-9d47-9454db59363c@gmx.com> (raw)
In-Reply-To: <0fdc35fdbc53f739fce1cb46ede8af97829aea11.1722441479.git.fdmanana@suse.com>
在 2024/8/1 01:29, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
>
> Currently we are redirecting stdout and stderr of fsstress to /dev/null.
> In case we have a test failure, it's useful to know the seed that
> fsstress was using because it might be helpful to run it again with that
> same seed in the hope of being able to reproduce the failure.
>
> So redirect stdout/stderr to the log file $seqres.full instead, so
> that we'll see a line like this after running the test:
>
> seed = 1722389488
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> tests/generic/019 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/generic/019 b/tests/generic/019
> index 26108be4..fe117ac8 100755
> --- a/tests/generic/019
> +++ b/tests/generic/019
> @@ -90,7 +90,7 @@ _workout()
> echo "Start fsstress.."
> echo ""
> echo "fsstress $args" >> $seqres.full
> - $FSSTRESS_PROG $args > /dev/null 2>&1 &
> + $FSSTRESS_PROG $args >> $seqres.full 2>&1 &
> fs_pid=$!
> echo "Start fio.."
> cat $fio_config >> $seqres.full
prev parent reply other threads:[~2024-07-31 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 15:59 [PATCH] generic/019: redirect fsstress output to log file instead fdmanana
2024-07-31 16:20 ` David Sterba
2024-07-31 23:29 ` 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=4bcf1b73-e59f-41fb-9d47-9454db59363c@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