From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH 1/6] test: Skip tst.depth.sh
Date: Mon, 30 Mar 2026 21:02:19 -0400 [thread overview]
Message-ID: <20260331010224.16165-1-eugene.loh@oracle.com> (raw)
From: Eugene Loh <eugene.loh@oracle.com>
The test asks for very many pid probes. E.g.,
pid$target:::entry,
pid$target:::return,
pid$target:a.out::,
If it is successful, this can wreak havoc on some systems, in some cases
leading to 1-2 dozen subsequent tests failing due to cascading problems:
poor test clean up, triggers left running, persistent loads, pid=0 not
running, tests timing out, and so on. These problems require
investigation.
For now, skip the precipitating test.
See
https://oss.oracle.com/pipermail/dtrace-devel/2025-November/006916.html
Incidentally, there are similar issues for
* test/unittest/pid/err.D_PROC_CREATEFAIL.many.d
but this test is already marked SKIP, apparently for the same reason.
See commit d9423bd79
("err.D_PROC_CREATEFAIL.many.d causes failures in subsequent tests").
The current patch simply seeks to apply the same SKIP to another test.
* test/demo/user/userfunc.d
but this test is marked XFAIL since it needs a trigger
All three tests should be resolved when the underlying problem is
tackled.
Orabug: 38642080
Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
test/unittest/ustack/tst.depth.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test/unittest/ustack/tst.depth.sh b/test/unittest/ustack/tst.depth.sh
index dec16a3aa..4a67291de 100755
--- a/test/unittest/ustack/tst.depth.sh
+++ b/test/unittest/ustack/tst.depth.sh
@@ -1,10 +1,10 @@
#!/bin/bash
#
# Oracle Linux DTrace.
-# Copyright (c) 2006, 2020, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2006, 2025, Oracle and/or its affiliates. All rights reserved.
# Licensed under the Universal Permissive License v 1.0 as shown at
# http://oss.oracle.com/licenses/upl.
-# @@xfail: dtv2
+# @@skip
if [ $# != 1 ]; then
echo expected one argument: '<'dtrace-path'>'
--
2.47.3
next reply other threads:[~2026-03-31 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 1:02 eugene.loh [this message]
2026-03-31 1:02 ` [PATCH 2/6] Simple typo in comment eugene.loh
2026-03-31 1:02 ` [PATCH 3/6] Check if the BPF PROG_LOAD is either -1 or else non-negative eugene.loh
2026-03-31 1:02 ` [PATCH 4/6] test: Remove unnecessary "destructive" pragma eugene.loh
2026-03-31 1:02 ` [PATCH 5/6] Possible uninitialized 'last' variable in usdt_copyin_data() eugene.loh
2026-03-31 1:02 ` [PATCH 6/6] test: Check declaration (without init) inside a probe eugene.loh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260331010224.16165-1-eugene.loh@oracle.com \
--to=eugene.loh@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox