xfstests: kill in 131 needs to be quiet
PATCH 1/1 xfstests: kill in 131 needs to be quiet
If the kill fails because the processes have already terminates, the output from kill (no such process) will cause the test to fail. Make sure kill doesn't output anything.
Signed-off-by Dave Chinner <[email protected]>
--- 131 | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
131 +2 -2
@@ -34,8 +34,8 @@ trap "_cleanup; exit \$status" 0 1 2 3 15 _cleanup() { - kill $locktest_pid2 - kill $locktest_pid1 + kill $locktest_pid2 2&>1 /dev/null + kill $locktest_pid1 2&>1 /dev/null _cleanup_testdir }
Signature · 6 lines
1.6.5 _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 5 lines · Dave Chinner
If the kill fails because the processes have already terminates, the output from kill (no such process) will cause the test to fail. Make sure kill doesn't output anything.
Signed-off-by Dave Chinner <[email protected]>
Yes, I see the same here,
Reviewed-by Christoph Hellwig <[email protected]>
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 11 lines · Christoph Hellwig
Quoted 5 lines · Dave Chinner
If the kill fails because the processes have already terminates, the output from kill (no such process) will cause the test to fail. Make sure kill doesn't output anything.
Signed-off-by Dave Chinner <[email protected]>Yes, I see the same here,
Reviewed-by Christoph Hellwig <[email protected]>
Pushed.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs