]> www.infradead.org Git - users/hch/xfstests-dev.git/commit
fstests: redirect fsstress' stdout to $seqres.full instead of /dev/null
authorFilipe Manana <fdmanana@suse.com>
Tue, 3 Oct 2023 11:57:44 +0000 (12:57 +0100)
committerZorro Lang <zlang@kernel.org>
Thu, 5 Oct 2023 14:32:01 +0000 (22:32 +0800)
commitf55e46d62968a3881bbe469e46a254978f517561
treef709f8983f5f88a968bea48f2e9c12fbdc657001
parent80e277fd69a2fd048c0e29f4749909041ac80925
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>
35 files changed:
tests/btrfs/028
tests/btrfs/049
tests/btrfs/060
tests/btrfs/061
tests/btrfs/062
tests/btrfs/063
tests/btrfs/064
tests/btrfs/065
tests/btrfs/066
tests/btrfs/067
tests/btrfs/068
tests/btrfs/069
tests/btrfs/070
tests/btrfs/071
tests/btrfs/072
tests/btrfs/073
tests/btrfs/074
tests/btrfs/136
tests/btrfs/192
tests/btrfs/232
tests/btrfs/261
tests/btrfs/286
tests/ext4/057
tests/ext4/307
tests/generic/068
tests/generic/269
tests/generic/409
tests/generic/410
tests/generic/411
tests/generic/589
tests/xfs/051
tests/xfs/057
tests/xfs/297
tests/xfs/305
tests/xfs/538