From: Kris Van Hees <kris.van.hees@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] test: Allow duplicate lines for rawfbt synthetic tests
Date: Wed, 19 Mar 2025 13:47:05 -0400 [thread overview]
Message-ID: <Z9sDGZvfbesX2728@oracle.com> (raw)
In-Reply-To: <20250319174225.2203-1-eugene.loh@oracle.com>
On Wed, Mar 19, 2025 at 01:42:25PM -0400, eugene.loh@oracle.com wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
>
> It is possible for the probe in these tests to fire "concurrently"
> on multiple CPUs, leading to duplicate lines of output. Add
> post processing to reduce multiple lines of duplicate output.
>
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
> ---
> test/unittest/providers/rawfbt/tst.synthetic-entry.r.p | 3 +++
> test/unittest/providers/rawfbt/tst.synthetic-return.r.p | 3 +++
> 2 files changed, 6 insertions(+)
> create mode 100755 test/unittest/providers/rawfbt/tst.synthetic-entry.r.p
> create mode 100755 test/unittest/providers/rawfbt/tst.synthetic-return.r.p
>
> diff --git a/test/unittest/providers/rawfbt/tst.synthetic-entry.r.p b/test/unittest/providers/rawfbt/tst.synthetic-entry.r.p
> new file mode 100755
> index 000000000..18171f044
> --- /dev/null
> +++ b/test/unittest/providers/rawfbt/tst.synthetic-entry.r.p
> @@ -0,0 +1,3 @@
> +#!/bin/sh
> +
> +uniq
> diff --git a/test/unittest/providers/rawfbt/tst.synthetic-return.r.p b/test/unittest/providers/rawfbt/tst.synthetic-return.r.p
> new file mode 100755
> index 000000000..18171f044
> --- /dev/null
> +++ b/test/unittest/providers/rawfbt/tst.synthetic-return.r.p
> @@ -0,0 +1,3 @@
> +#!/bin/sh
> +
> +uniq
> --
> 2.43.5
>
prev parent reply other threads:[~2025-03-19 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 17:42 [PATCH] test: Allow duplicate lines for rawfbt synthetic tests eugene.loh
2025-03-19 17:47 ` Kris Van Hees [this message]
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=Z9sDGZvfbesX2728@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