public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH] test: Increase syscall entry timeout
Date: Thu, 22 Jan 2026 17:01:54 -0500	[thread overview]
Message-ID: <20260122220154.20552-1-eugene.loh@oracle.com> (raw)

From: Eugene Loh <eugene.loh@oracle.com>

The run time for this test seems twice as long for aarch64 as for
x86_64.  Further, the run time seems to have jumped significantly from
kernel 5.15 to 6.12 and then again to kernel 6.18.  E.g.,

                  x86_64     aarch64
    5.15          7 secs     18 secs
    6.12         12 secs     33 secs
    6.18         22 secs     54 secs

Looking at a run on the 6.18 aarch64 system, the time is basically
spent in the dtrace_close() call to dt_probe_detach_all(), which does:

    for (prp = ...)
        prp->prov->impl->detach(dtp, prp);

Then, dt_tp_probe_detach() calls dt_tp_detach(), which does:

    close(tpp->fd);

This close() averages over 0.1 secs.  For hundreds of syscall probes,
we get nearly a minute of run time, exceeding the default test timeout.

For the time being, increase the timeout on this test.

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
 test/unittest/syscall/tst.entry.d | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/test/unittest/syscall/tst.entry.d b/test/unittest/syscall/tst.entry.d
index f2d56150d..dfd7304e5 100644
--- a/test/unittest/syscall/tst.entry.d
+++ b/test/unittest/syscall/tst.entry.d
@@ -1,6 +1,6 @@
 /*
  * Oracle Linux DTrace.
- * Copyright (c) 2020, Oracle and/or its affiliates. All rights reserved.
+ * Copyright (c) 2020, 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.
  */
@@ -8,6 +8,7 @@
 /* @@trigger: syscall-tst-args */
 /* @@trigger-timing: before */
 /* @@runtest-opts: $_pid */
+/* @@timeout: 80 */
 
 /* check that syscall:::entry picks up mmap:entry */
 /* (mmap is called repeatedly by the trigger) */
-- 
2.47.3


             reply	other threads:[~2026-01-22 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 22:01 eugene.loh [this message]
2026-01-27 12:56 ` [DTrace-devel] [PATCH] test: Increase syscall entry timeout Nick Alcock

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=20260122220154.20552-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