From: Nick Alcock <nix@esperi.org.uk>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 18/20] test: use fully qualified probe descriptions
Date: Fri, 06 Nov 2026 13:38:51 +0000 [thread overview]
Message-ID: <87tsluqduc.fsf@esperi.org.uk> (raw)
In-Reply-To: <f8d62d6bda17dac591158d0bdedffef8@oracle.com>
On 30 Oct 2026, Kris Van Hees verbalised:
> Qualify probe descriptions in standalone D tests, embedded and generated D
> programs, and preprocessor definitions. Update expected diagnostics that
> echo the qualified descriptions.
>
> Preserve abbreviated or invalid descriptions where probe specification or
> matching is the subject of the test.
This has been long needed and long put off by everyone :) I suppose it
only really matters now that systemwide uprobes can introduce entirely
arbitrary new probe names that might match any of these.
I looked at a few, they look reaonable, and checked the match-specific
ones. If these had genuinely broken anything, at least the non-XFAILed
ones would be screaming, too. (Did you check the XFAILed ones' log
output to make sure they weren't failing for new reasons now?)
Reviewed-by: Nick Alcock <nix@esperi.org.uk>
--
NULL && (void)
prev parent reply other threads:[~2026-11-06 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:37 [PATCH 18/20] test: use fully qualified probe descriptions Kris Van Hees
2026-11-06 13:38 ` 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=87tsluqduc.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@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