From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v2] test: Wait for output to flush out in enable_pid
Date: Wed, 30 Jul 2025 18:39:48 -0400 [thread overview]
Message-ID: <aIqfNKgdHaS6R6Nz@oracle.com> (raw)
In-Reply-To: <251f2ae1-a884-4a97-49e0-c0fb419a92f3@oracle.com>
On Wed, Jul 30, 2025 at 06:03:39PM -0400, Eugene Loh wrote:
> On 7/30/25 10:26, Kris Van Hees wrote:
>
> > On Wed, Jul 30, 2025 at 10:18:17AM -0400, Kris Van Hees via DTrace-devel wrote:
> > > I still see intermittent FAILs. I wonder whether there is a potentially unsafe
> > > contruct at work (see below).
> > Hm, no that does not fix it either.
> >
> > Eugene - can you have a closer look at this and see what might be going on?
>
> I ran 40x on each of my 11 test VMs and am unable to get a FAIL with this
> patch. I took a look at the test some more, but without a failure it's hard
> to fix.
>
> Are you saying there is missing output (the motivating problem) or that
> there is a timeout (I thought you may have said this, but I cannot find
> where)? Those would seem to be two separate problems, the latter being that
> a trigger does not see 4 signals.
Here is the issue:
Diff against expected:
--- test/unittest/usdt/tst.enable_pid.r 2025-06-08 00:17:54.789469056 -0400
+++ /tmp/runtest.18085/test.out 2025-07-30 10:23:48.697293799 -0400
@@ -22,8 +22,6 @@
=== epoch ===
is not enabled
is enabled
-is not enabled
-=== epoch ===
========== out 2
is not enabled
=== epoch ===
next prev parent reply other threads:[~2025-07-30 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 22:30 [PATCH v2] test: Wait for output to flush out in enable_pid eugene.loh
2025-07-22 13:38 ` Nick Alcock
2025-07-29 14:13 ` [DTrace-devel] " Kris Van Hees
2025-07-29 15:19 ` Kris Van Hees
2025-07-30 14:18 ` Kris Van Hees
2025-07-30 14:26 ` [DTrace-devel] " Kris Van Hees
2025-07-30 22:03 ` Eugene Loh
2025-07-30 22:39 ` Kris Van Hees [this message]
2025-07-31 0:17 ` Kris Van Hees
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=aIqfNKgdHaS6R6Nz@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
/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