public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: dtrace-devel@oss.oracle.com, dtrace@lists.linux.dev
Subject: Re: [DTrace-devel] [PATCH v2] Fix flowindent for "return" probes with multiple statements
Date: Tue, 14 Apr 2026 22:31:19 +0100	[thread overview]
Message-ID: <87eckh2pqw.fsf@esperi.org.uk> (raw)
In-Reply-To: <20260330011343.8596-1-eugene.loh@oracle.com> (eugene loh's message of "Sun, 29 Mar 2026 21:13:43 -0400")

On 30 Mar 2026, eugene loh spake thusly:

> From: Eugene Loh <eugene.loh@oracle.com>
>
> The flowindent algorithm should change indentation based only on the
> number of levels of entry and return.  So, if an entry or return probe
> has multiple statements, the indentation should change only for the
> first statement.
>
> Such logic is used for entry probes.  Similar logic should be used for
> return probes.
>
> Add a test to cover the case of multiple statements per entry and return
> probes.  Also have it check a greater number of indentations.  Since
> the new test supersedes the old ones, remove the old tests, which
> were fickle anyhow.  The new test can still fail -- the flowindent
> algorithm is not completely robust -- so allow reinvocation in case of
> failure.  The intermittent failures of flowindent tests have long been a
> testing irritant.  Now, with reinvocation, testing shows no failures in
> 100 iterations on over a dozen systems.
>
> Orabug: 39140395
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>

Reviewed-by: Nick Alcock <nick.alcock@oracle.com>

Much better tests!

-- 
NULL && (void)

      reply	other threads:[~2026-04-14 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30  1:13 [PATCH v2] Fix flowindent for "return" probes with multiple statements eugene.loh
2026-04-14 21:31 ` 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=87eckh2pqw.fsf@esperi.org.uk \
    --to=nick.alcock@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