From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH 1/2] test: Skip tst.aggmod_full2.sh
Date: Wed, 18 Mar 2026 17:48:25 -0400 [thread overview]
Message-ID: <20260318214826.6296-1-eugene.loh@oracle.com> (raw)
From: Eugene Loh <eugene.loh@oracle.com>
The test was only being run on older x86 systems, where it had been
failing consistently for a long time. Since kernels are moving from
kallmodsyms to modules.builtin.ranges, we do not care much about such
problems.
Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
test/unittest/aggs/tst.aggmod_full2.x | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/test/unittest/aggs/tst.aggmod_full2.x b/test/unittest/aggs/tst.aggmod_full2.x
index 3660504ad..a530a3d2d 100755
--- a/test/unittest/aggs/tst.aggmod_full2.x
+++ b/test/unittest/aggs/tst.aggmod_full2.x
@@ -1,10 +1,25 @@
#!/bin/bash
#
# Oracle Linux DTrace.
-# Copyright (c) 2018, 2024, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2018, 2026, 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.
+# Let us skip this test altogether:
+# * The test was never vetted on arm.
+# * The test does not run on newer kernels since they have no kallmodsyms.
+# * On older x86 platforms, the test has failed consistently for a long time.
+# The test had been intended for checking /proc/kallmodsyms,
+# but we are migrating to a modules.builtin.ranges approach.
+# When we are absolutely sure we do not care about this test, it can be removed.
+
+echo "test is deprecated"
+exit 2
+
+###############################################
+### The older contents of this file follow. ###
+###############################################
+
# The test still needs to be vetted on ARM64, including for copyinstr() support.
# Once it runs on ARM64, the slower tst.aggmod_full.sh test can be removed.
--
2.47.3
next reply other threads:[~2026-03-18 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 21:48 eugene.loh [this message]
2026-03-18 21:48 ` [PATCH 2/2] docs: Include provider names in probe references 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=20260318214826.6296-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