diff options
| author | Filipe Manana <fdmanana@suse.com> | 2023-10-03 12:57:44 +0100 |
|---|---|---|
| committer | Zorro Lang <zlang@kernel.org> | 2023-10-05 22:32:01 +0800 |
| commit | f55e46d62968a3881bbe469e46a254978f517561 (patch) | |
| tree | f709f8983f5f88a968bea48f2e9c12fbdc657001 /tests/btrfs/067 | |
| parent | 80e277fd69a2fd048c0e29f4749909041ac80925 (diff) | |
fstests: redirect fsstress' stdout to $seqres.full instead of /dev/null
Several tests are redirecting the output of fsstress to /dev/null and this
makes it harder to debug a test failure because we have no way of knowing
what was the seed used by fsstress, as fsstress outputs the seed it uses
to stdout. Very often when such a test fails, I have to go modify to
redirect stdout to the $seqres.full file and then run it in a loop until
I find a seed that causes a failure.
So modify all tests that redirect fsstress' output to /dev/null to instead
redirect it to the $seqres.full file. Note that for some tests I've added
the style ">> $seqres.full" (with a space after >>) while for others I did
">>$seqres.full" (no space) - the reason for this was to keep style
consistency within each test case.
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Acked-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>
Diffstat (limited to 'tests/btrfs/067')
| -rwxr-xr-x | tests/btrfs/067 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/btrfs/067 b/tests/btrfs/067 index 970a23c4..709db155 100755 --- a/tests/btrfs/067 +++ b/tests/btrfs/067 @@ -39,7 +39,7 @@ run_test() args=`_scale_fsstress_args -p 20 -n 100 $FSSTRESS_AVOID -d $SCRATCH_MNT/stressdir` echo "Run fsstress $args" >>$seqres.full - $FSSTRESS_PROG $args >/dev/null 2>&1 & + $FSSTRESS_PROG $args >>$seqres.full & fsstress_pid=$! # make sure the stop sign is not there |