From: Nick Alcock <nick.alcock@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH v2] test: Wait for output to flush out in enable_pid
Date: Tue, 22 Jul 2025 14:38:55 +0100 [thread overview]
Message-ID: <877c005or4.fsf@esperi.org.uk> (raw)
In-Reply-To: <20250628223050.3396-1-eugene.loh@oracle.com> (eugene loh's message of "Sat, 28 Jun 2025 18:30:50 -0400")
On 28 Jun 2025, eugene loh said:
> From: Eugene Loh <eugene.loh@oracle.com>
>
> Our luck with this test has been quite good, but it sometimes fails
> to show its last lines of output. That is, we send a USR1 to the
> trigger processes to set off the final output and we immediately
> cat the output files. If there is any delay in handling the signal,
> the last output will be missing.
>
> Have the processes terminate themselves when their last output is
> flushed; then wait for those processes. Also, skip testing altogether if
> there is only a single processor to run the two, hard-spinning processes.
Yeah, much better design.
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
--
NULL && (void)
next prev parent reply other threads:[~2025-07-22 13: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 [this message]
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
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=877c005or4.fsf@esperi.org.uk \
--to=nick.alcock@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