[DTrace-devel] [PATCH v2 3/7] test: change test trigger and timeout
Kris Van Hees
kris.van.hees at oracle.com
Tue Nov 18 16:38:01 UTC 2025
This test requires a trigger that has symbol information to ensure that
we can trace functions in it. Also, due to the large amount of probes
being placed in this test, a much longer timeout is needed to ensure that
the test does not get killed by the test harness. Premature killing of
the test results in deferred cleanup being done at the kernel level, and
while that is going on, subsequent tests may be negatively affected.
Signed-off-by: Kris Van Hees <kris.van.hees at oracle.com>
---
- Changed title from v1
---
test/unittest/ustack/tst.depth.sh | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/test/unittest/ustack/tst.depth.sh b/test/unittest/ustack/tst.depth.sh
index dec16a3a..8f99204c 100755
--- a/test/unittest/ustack/tst.depth.sh
+++ b/test/unittest/ustack/tst.depth.sh
@@ -5,6 +5,7 @@
# Licensed under the Universal Permissive License v 1.0 as shown at
# http://oss.oracle.com/licenses/upl.
# @@xfail: dtv2
+# @@timeout: 600
if [ $# != 1 ]; then
echo expected one argument: '<'dtrace-path'>'
@@ -16,11 +17,9 @@ dtrace=$1
rm -f $file
-$dtrace $dt_flags -o $file -c date -s /dev/stdin <<EOF
+$dtrace $dt_flags -o $file -c ./test/triggers/mmap -s /dev/stdin <<EOF
#pragma D option quiet
- #pragma D option bufsize=1M
- #pragma D option bufpolicy=fill
pid\$target:::entry,
pid\$target:::return,
@@ -45,7 +44,7 @@ $dtrace $dt_flags -o $file -c date -s /dev/stdin <<EOF
EOF
status=$?
-if [ "$status" -ne 0 ]; then
+if [ $status -ne 0 ]; then
echo $tst: dtrace failed
rm -f $file
exit $status
@@ -78,8 +77,8 @@ EOF
status=$?
-count=`wc -l $file | cut -f1 -do`
-if [ "$count" -lt 1000 ]; then
+count=`wc -l $file | cut -f1 -d' '`
+if [ $count -lt 1000 ]; then
echo $tst: output was too short
status=1
fi
--
2.43.5
More information about the DTrace-devel
mailing list