Remove `du' stack space test.

Apparently, `ulimit -s N' isn't portable enough.
This test will be restored (with a guard against losing ulimit)
in its own file later.

diff --git a/tests/rm/deep-1 b/tests/rm/deep-1
index 0ff781ea0d45a9f94e6db9020e33c643985f90eb..e995c54c541074a69ac5338edf4589632380da33 100755 (executable)
--- a/tests/rm/deep-1
+++ b/tests/rm/deep-1
@@ -1,7 +1,6 @@
 #!/bin/sh
 
 # This is a bit of a torture test for mkdir -p, too.
-# Also make sure du can process this tree without using too much stack space.
 # GNU rm performs *much* better on systems that have a d_type member
 # in the directory structure because then it does only one stat per
 # command line argument.
@@ -37,13 +36,6 @@ mkdir -p $deep || fail=1
 # Make sure the deep dir was created.
 test -d $deep || fail=1
 
-# Make sure du can handle it without using lots of stack.
-# Before switching to the non-recursive, fts-based version of du,
-# this invocation of du would require a stack of at least 115KB
-# on an x86 linux-2.4.22 system.  The fts-based version needs
-# only 8KB on that same system.
-( ulimit -s 50; du -s $tmp > /dev/null ) || fail=1
-
 rm -r $tmp || fail=1
 
 # Make sure all of $tmp was deleted.