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] test: Wait for output to flush out in enable_pid
Date: Fri, 13 Jun 2025 15:15:44 +0100 [thread overview]
Message-ID: <878qlvenhr.fsf@esperi.org.uk> (raw)
In-Reply-To: <20250608053620.15468-1-eugene.loh@oracle.com> (eugene loh's message of "Sun, 8 Jun 2025 01:36:20 -0400")
On 8 Jun 2025, eugene loh told this:
> 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, the last output will
> be missing.
>
> Add a short delay so that the last output will be seen.
Unavoidable if it's structured this way, but if you hit them with a USR2
and caught USR2 and had that do the same output as USR1 and then exit(),
and did a wait(1) for both of them, you could avoid this delay.
--
NULL && (void)
prev parent reply other threads:[~2025-06-13 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 5:36 [PATCH] test: Wait for output to flush out in enable_pid eugene.loh
2025-06-13 14:15 ` Nick Alcock [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=878qlvenhr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.