generic/269: Fix failure due to race killing fsstress job
authorFilipe Manana <fdmanana@suse.com>
Tue, 17 Nov 2015 03:44:45 +0000 (14:44 +1100)
committerDave Chinner <david@fromorbit.com>
Tue, 17 Nov 2015 03:44:45 +0000 (14:44 +1100)
commite597459397acad3fcb19fa00e8a4abb8a59f8af2
tree41537a7d58e668fb6fe8bb59e01b1c12bbf7a54e
parentb056c775021a2d6330104d9882791981706b9261
generic/269: Fix failure due to race killing fsstress job

When running the test generic/269 against a fast scratch device (loopback
device backed by a file on tmpfs) I often got a test failure due to the
fact that the fsstress job had already completed before the test attempted
to kill it, producing the following failure output:

generic/269 91s ... - output mismatch (see .../generic/269.out.bad)
    --- tests/generic/269.out 2014-11-17 20:59:50.974203000 +0000
    +++ /home/fdmanana/git/hub/xfstests/results//generic/269.out.bad 2015-11-13 15:41:59.669893035 +0000
    @@ -3,3 +3,4 @@
     Run fsstress

     Run dd writers in parallel
    +./tests/generic/269: line 59: kill: (13417) - No such process
    ...
    (Run 'diff -u tests/generic/269.out .../generic/269.out.bad'  to see the entire diff)

So fix this false failure by redirecting the standard output and error
from the kill into the seq file.

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
tests/generic/269