From: Jim Meyering <meyering@redhat.com>
Date: Wed, 30 Sep 2009 21:28:13 +0000 (+0200)
Subject: tests: tail-2/pid: use a 3-second timeout, not 1
X-Git-Tag: v8.0~9
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=30a227673eb4b095563c0ff75c6d89a7cae5096a;p=thirdparty%2Fcoreutils.git

tests: tail-2/pid: use a 3-second timeout, not 1

* tests/tail-2/pid: When using the timeout program to ensuring that
tail -s.1 --pid=$PID_T_MAX does not wait forever, use a timeout longer
than 1 second.  A 1-second timeout could be too short on a very busy
system, and result in a timeout, and hence false-positive failure.

2009-09-30  Jim Meyering  <meyering@redhat.com>
---

diff --git a/tests/tail-2/pid b/tests/tail-2/pid
index aaf2e01ba8..90f1684304 100755
--- a/tests/tail-2/pid
+++ b/tests/tail-2/pid
@@ -42,13 +42,13 @@ for inotify in ---disable-inotify ''; do
 
   # Ensure that tail --pid=PID exits successfully when PID is dead.
   # Use an unlikely-to-be-live PID
-  timeout 1 tail -s.1 --pid=$PID_T_MAX -f $inotify /dev/null
+  timeout 3 tail -s.1 --pid=$PID_T_MAX -f $inotify /dev/null
   ret=$?
   test $ret = 124 && skip_test_ "pid $PID_T_MAX present"
   test $ret = 0 || fail=1
 
   # Ensure fractional sleep parameter is honored with --pid
-  timeout 1 tail -s.1 -f $inotify /dev/null --pid=$PID_T_MAX
+  timeout 3 tail -s.1 -f $inotify /dev/null --pid=$PID_T_MAX
   test $? = 124 && fail=1
 done