Merge branch 'master' of ssh://sources.redhat.com/git/systemtap

16 files changed, 16 insertions, 16 deletions

diff --git a/testsuite/systemtap.examples/process/chng_cpu.meta b/testsuite/systemtap.examples/process/chng_cpu.meta
index 944f417a..7be73b78 100644
--- a/testsuite/systemtap.examples/process/chng_cpu.meta
+++ b/testsuite/systemtap.examples/process/chng_cpu.meta
@@ -11,4 +11,4 @@ scope: pid
 description: The chng_cpu.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name is found running on a different processor, the script prints out the thread id (tid), the executable name, the processor now running the task, the thread state, and a backtrace showing the kernel functions that triggered the running of the task on the processor.
 arg_1: The name of the executable to monitor
 test_check: stap -p4 chng_cpu.stp bash
-test_installcheck: stap chng_cpu.stp -c "sleep 1" bash
+test_installcheck: stap chng_cpu.stp -c "sleep 0.2" bash
diff --git a/testsuite/systemtap.examples/process/errsnoop.meta b/testsuite/systemtap.examples/process/errsnoop.meta
index 34b8cb7c..8afcdd96 100644
--- a/testsuite/systemtap.examples/process/errsnoop.meta
+++ b/testsuite/systemtap.examples/process/errsnoop.meta
@@ -4,4 +4,4 @@ keywords: process syscall
 subsystem: general
 description: The script prints a periodic tabular report about failing system calls, by process and by syscall failure.  The first optional argument specifies the reporting interval (in seconds, default 5); the second optional argument gives a screen height (number of lines in the report, default 20).
 test_check: stap -p4 errsnoop.stp
-test_installcheck: stap errsnoop.stp 1 10 -c "sleep 3"
+test_installcheck: stap errsnoop.stp 1 10 -c "sleep 1"
diff --git a/testsuite/systemtap.examples/process/forktracker.meta b/testsuite/systemtap.examples/process/forktracker.meta
index 87d43d7a..2ba3a659 100644
--- a/testsuite/systemtap.examples/process/forktracker.meta
+++ b/testsuite/systemtap.examples/process/forktracker.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The forktracker.stp script prints out a time-stamped entry showing each fork and exec operation on the machine. This can be useful for determine what process is creating a flurry of short-lived processes.
 test_check: stap -p4 forktracker.stp
-test_installcheck: stap forktracker.stp -c "sleep 1"
+test_installcheck: stap forktracker.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/futexes.meta b/testsuite/systemtap.examples/process/futexes.meta
index ff303122..404f576d 100644
--- a/testsuite/systemtap.examples/process/futexes.meta
+++ b/testsuite/systemtap.examples/process/futexes.meta
@@ -10,4 +10,4 @@ output: sorted-list on-exit
 scope: system-wide
 description: The script watches the futex syscall on the system. On exit the futexes address, the number of contentions, and the average time for each contention on the futex are printed from lowest pid number to highest.
 test_check: stap -p4 futexes.stp
-test_installcheck: stap futexes.stp -c "sleep 1"
+test_installcheck: stap futexes.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/migrate.meta b/testsuite/systemtap.examples/process/migrate.meta
index 09a25de0..24e8bdc9 100644
--- a/testsuite/systemtap.examples/process/migrate.meta
+++ b/testsuite/systemtap.examples/process/migrate.meta
@@ -11,4 +11,4 @@ scope: pid
 description: The migrate.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name migrates between processors an entry is printed with the process id (pid), the executable name, the processor off loading the task, and the process taking the task. Note that the task may or may not be executing at the time of the migration.
 arg_1: The name of the executable to watch
 test_check: stap -p4 migrate.stp bash
-test_installcheck: stap migrate.stp -c "sleep 1" bash
+test_installcheck: stap migrate.stp -c "sleep 0.2" bash
diff --git a/testsuite/systemtap.examples/process/pf2.meta b/testsuite/systemtap.examples/process/pf2.meta
index d0a534bd..8fa14d04 100644
--- a/testsuite/systemtap.examples/process/pf2.meta
+++ b/testsuite/systemtap.examples/process/pf2.meta
@@ -10,4 +10,4 @@ output: sorted-list
 scope: system-wide
 description: The pf2.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top ten kernel functions with samples.
 test_check: stap -p4 pf2.stp
-test_installcheck: stap pf2.stp -c "sleep 1"
+test_installcheck: stap pf2.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/schedtimes.meta b/testsuite/systemtap.examples/process/schedtimes.meta
index 786d9cfb..960d8eda 100644
--- a/testsuite/systemtap.examples/process/schedtimes.meta
+++ b/testsuite/systemtap.examples/process/schedtimes.meta
@@ -11,4 +11,4 @@ scope: system-wide
 description: The schedtimes.stp script instruments the scheduler to track the amount of time that each process spends running, sleeping, queued, and waiting for io. On exit the script prints out the accumulated time for each state of processes observed.  Optionally, this script can be used with the '-c' or '-x' options to focus on a specific PID.
 test_support: stap -l kernel.trace("sched_switch"),kernel.trace("sched_wakeup")
 test_check: stap -p4 schedtimes.stp
-test_installcheck: stap schedtimes.stp -c "sleep 1"
+test_installcheck: stap schedtimes.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/sig_by_pid.meta b/testsuite/systemtap.examples/process/sig_by_pid.meta
index 03b02fba..7f371151 100644
--- a/testsuite/systemtap.examples/process/sig_by_pid.meta
+++ b/testsuite/systemtap.examples/process/sig_by_pid.meta
@@ -10,4 +10,4 @@ output: sorted-list on-exit
 scope: system-wide
 description: Print signal counts by process ID in descending order.
 test_check: stap -p4 sig_by_pid.stp
-test_installcheck: stap sig_by_pid.stp -c "sleep 1"
+test_installcheck: stap sig_by_pid.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/sig_by_proc.meta b/testsuite/systemtap.examples/process/sig_by_proc.meta
index eea42be4..8a454373 100644
--- a/testsuite/systemtap.examples/process/sig_by_proc.meta
+++ b/testsuite/systemtap.examples/process/sig_by_proc.meta
@@ -10,4 +10,4 @@ output: sorted-list on-exit
 scope: system-wide
 description: Print signal counts by process name in descending order.
 test_check: stap -p4 sig_by_proc.stp
-test_installcheck: stap sig_by_proc.stp -c "sleep 1"
+test_installcheck: stap sig_by_proc.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/sigkill.meta b/testsuite/systemtap.examples/process/sigkill.meta
index 57032224..b0e04ce8 100644
--- a/testsuite/systemtap.examples/process/sigkill.meta
+++ b/testsuite/systemtap.examples/process/sigkill.meta
@@ -11,4 +11,4 @@ scope: systemwide
 description: The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the desination executable and process ID, the executable name user ID that sent the signal.
 arg_1: The name of the signal to look for on selected process.
 test_check: stap -p4 sigkill.stp
-test_installcheck: stap sigkill.stp -c "sleep 1"
+test_installcheck: stap sigkill.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/sigmon.meta b/testsuite/systemtap.examples/process/sigmon.meta
index fe192248..03c54f96 100644
--- a/testsuite/systemtap.examples/process/sigmon.meta
+++ b/testsuite/systemtap.examples/process/sigmon.meta
@@ -11,4 +11,4 @@ scope: pid
 description: The script watches for a particular signal sent to a specific process. When that signal is sent to the specified process, the script prints out the PID and executable of the process sending the signal, the PID and executable name of the process receiving the signal, and the signal number and name.
 arg_1: The name of the signal to look for on selected process.
 test_check: stap -p4 sigmon.stp SIGKILL
-test_installcheck: stap sigmon.stp -c "sleep 1" SIGKILL
+test_installcheck: stap sigmon.stp -c "sleep 0.2" SIGKILL
diff --git a/testsuite/systemtap.examples/process/sleepingBeauties.meta b/testsuite/systemtap.examples/process/sleepingBeauties.meta
index 3338edbf..b2692ba0 100644
--- a/testsuite/systemtap.examples/process/sleepingBeauties.meta
+++ b/testsuite/systemtap.examples/process/sleepingBeauties.meta
@@ -4,4 +4,4 @@ keywords: io scheduler backtrace
 subsystem: scheduler
 description: The script monitors the time that threads spend waiting for IO operations (in "D" state) in the wait_for_completion function.  If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.
 test_check: stap -p4 sleepingBeauties.stp
-test_installcheck: stap sleepingBeauties.stp -c "sleep 1"
+test_installcheck: stap sleepingBeauties.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/sleeptime.meta b/testsuite/systemtap.examples/process/sleeptime.meta
index d6c59345..7318c7aa 100644
--- a/testsuite/systemtap.examples/process/sleeptime.meta
+++ b/testsuite/systemtap.examples/process/sleeptime.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The script watches each nanosleep syscall on the system. At the end of each nanosleep syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "nanosleep:" key, and the duration of the sleep in microseconds.
 test_check: stap -p4 sleeptime.stp
-test_installcheck: stap sleeptime.stp -c "sleep 1"
+test_installcheck: stap sleeptime.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/syscalls_by_pid.meta b/testsuite/systemtap.examples/process/syscalls_by_pid.meta
index 590652b3..65bb97ac 100644
--- a/testsuite/systemtap.examples/process/syscalls_by_pid.meta
+++ b/testsuite/systemtap.examples/process/syscalls_by_pid.meta
@@ -10,4 +10,4 @@ output: sorted-list on-exit
 scope: system-wide
 description: The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each PID ordered from greatest to least number of syscalls.
 test_check: stap -p4 syscalls_by_pid.stp
-test_installcheck: stap syscalls_by_pid.stp -c "sleep 1"
+test_installcheck: stap syscalls_by_pid.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/syscalls_by_proc.meta b/testsuite/systemtap.examples/process/syscalls_by_proc.meta
index 79aa3e87..42668bc8 100644
--- a/testsuite/systemtap.examples/process/syscalls_by_proc.meta
+++ b/testsuite/systemtap.examples/process/syscalls_by_proc.meta
@@ -10,4 +10,4 @@ output: sorted-list on-exit
 scope: system-wide
 description: The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greates to least number of syscalls.
 test_check: stap -p4 syscalls_by_proc.stp
-test_installcheck: stap syscalls_by_proc.stp -c "sleep 1"
+test_installcheck: stap syscalls_by_proc.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/process/wait4time.meta b/testsuite/systemtap.examples/process/wait4time.meta
index a939d466..e798014b 100644
--- a/testsuite/systemtap.examples/process/wait4time.meta
+++ b/testsuite/systemtap.examples/process/wait4time.meta
@@ -10,4 +10,4 @@ output: trace
 scope: system-wide
 description: The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in paretheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".
 test_check: stap -p4 wait4time.stp
-test_installcheck: stap wait4time.stp -c "sleep 1"
+test_installcheck: stap wait4time.stp -c "sleep 0.2"