Make check.exp not sleep so much in test_installcheck.

A lot of time during the installcheck was spend just sleeping. Reduce the
sleep time by at least one fifth.

* testsuite/systemtap.examples/*/*meta: Reduct -c "sleep" time.

7 files changed, 7 insertions, 7 deletions

diff --git a/testsuite/systemtap.examples/network/autofs4.meta b/testsuite/systemtap.examples/network/autofs4.meta
index c6886e1c..e0036481 100644
--- a/testsuite/systemtap.examples/network/autofs4.meta
+++ b/testsuite/systemtap.examples/network/autofs4.meta
@@ -6,4 +6,4 @@ keywords: network autofs nfs
 subsystem: network
 test_support: stap -l module("autofs4").function("autofs4_lookup"),module("autofs4").function("autofs4_follow_link"),module("autofs4").function("autofs4_expire_indirect").return,module("autofs4").function("autofs4_wait").return
 test_check: stap -p4 autofs4.stp
-test_installcheck: stap autofs4.stp -c "sleep 10"
+test_installcheck: stap autofs4.stp -c "sleep 1"
diff --git a/testsuite/systemtap.examples/network/dropwatch.meta b/testsuite/systemtap.examples/network/dropwatch.meta
index 98b23e05..06d338c5 100644
--- a/testsuite/systemtap.examples/network/dropwatch.meta
+++ b/testsuite/systemtap.examples/network/dropwatch.meta
@@ -11,4 +11,4 @@ scope: system-wide
 description: Every five seconds the dropwatch.stp script lists the number of socket buffers freed at locations in the kernel.
 test_support: stap -l kernel.trace("kfree_skb")
 test_check: stap -p4 dropwatch.stp
-test_installcheck: stap dropwatch.stp -c "sleep 1"
+test_installcheck: stap dropwatch.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/network/nettop.meta b/testsuite/systemtap.examples/network/nettop.meta
index 61d1c153..1c3923c7 100644
--- a/testsuite/systemtap.examples/network/nettop.meta
+++ b/testsuite/systemtap.examples/network/nettop.meta
@@ -10,4 +10,4 @@ output: timed
 scope: system-wide
 description: Every five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.
 test_check: stap -p4 nettop.stp
-test_installcheck: stap nettop.stp -c "sleep 1"
+test_installcheck: stap nettop.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/network/sk_stream_wait_memory.meta b/testsuite/systemtap.examples/network/sk_stream_wait_memory.meta
index bc798f72..186203a1 100644
--- a/testsuite/systemtap.examples/network/sk_stream_wait_memory.meta
+++ b/testsuite/systemtap.examples/network/sk_stream_wait_memory.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The sk_stream-wait_memory.stp prints a time stamp, executable, and pid each time a process blocks due to the send buffer being full. A similar entry is printed each time a process continues because there is room in the buffer.
 test_check: stap -p4 sk_stream_wait_memory.stp
-test_installcheck: stap sk_stream_wait_memory.stp -c "sleep 1"
+test_installcheck: stap sk_stream_wait_memory.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/network/socket-trace.meta b/testsuite/systemtap.examples/network/socket-trace.meta
index 0b26f2fe..f73731b5 100644
--- a/testsuite/systemtap.examples/network/socket-trace.meta
+++ b/testsuite/systemtap.examples/network/socket-trace.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The script instrument each of the functions inn the Linux kernel's net/socket.c file. The script prints out trace. The first element of a line is  time delta in microseconds from the previous entry. This is followed by the command name and the PID. The "->" and "<-" indicates function entry and  function exit, respectively. The last element of the line is the function name.
 test_check: stap -p4 socket-trace.stp
-test_installcheck: stap socket-trace.stp -c "sleep 1"
+test_installcheck: stap socket-trace.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/network/tcp_connections.meta b/testsuite/systemtap.examples/network/tcp_connections.meta
index 0bc9bcb1..df24850d 100644
--- a/testsuite/systemtap.examples/network/tcp_connections.meta
+++ b/testsuite/systemtap.examples/network/tcp_connections.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The tcp_connections.stp script prints information for each new incoming TCP connection accepted by the computer. The information includes the UID, the command accepting the connection, the PID of the command, the port the connection is on, and the IP address of the originator of the request.
 test_check: stap -p4 tcp_connections.stp
-test_installcheck: stap tcp_connections.stp -c "sleep 1"
+test_installcheck: stap tcp_connections.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/network/tcpdumplike.meta b/testsuite/systemtap.examples/network/tcpdumplike.meta
index 0de45d5e..f5975aa6 100644
--- a/testsuite/systemtap.examples/network/tcpdumplike.meta
+++ b/testsuite/systemtap.examples/network/tcpdumplike.meta
@@ -10,4 +10,4 @@ output: timed
 scope: system-wide
 description: The tcpdumplike.stp prints out a line for each TCP packet received. Each line includes the source and destination IP addresses, the source and destination ports, and flags.
 test_check: stap -p4 tcpdumplike.stp
-test_installcheck: stap tcpdumplike.stp -c "sleep 1"
+test_installcheck: stap tcpdumplike.stp -c "sleep 0.2"