From: Nick Alcock <nick.alcock@oracle.com>
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Cc: eugene.loh@oracle.com
Subject: Re: [PATCH 2/5] proc: more self-grab improvements
Date: Tue, 03 Dec 2024 13:43:57 +0000 [thread overview]
Message-ID: <87frn43mqq.fsf@esperi.org.uk> (raw)
In-Reply-To: <20241203113610.75104-3-nick.alcock@oracle.com> (Nick Alcock's message of "Tue, 3 Dec 2024 11:36:07 +0000")
On 3 Dec 2024, Nick Alcock outgrape:
> This has survived a thousand iterations of test/unittest/proc/tst.self-grab.sh
> and test/unittest/usdt/tst.multitrace.sh with no failures (after the other
> patches in this series are applied).
Also survived internals/libproc tests (just making sure I didn't break
grabbing in a more fundamental way):
1300 cases (1100 PASS, 0 FAIL, 0 XPASS, 200 XFAIL, 0 SKIP)
(and survived a more conventional full test run as well).
Alas tst.lmid-consistency.sh is still failing: I must figure out why and
fix it one of these days, now lmids are becoming slightly less
absolutely useless on very modern glibc.
next prev parent reply other threads:[~2024-12-03 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:36 [PATCH 0/5] fix test/unittest/usdt/tst.multitrace.sh Nick Alcock
2024-12-03 11:36 ` [PATCH 1/5] Revert "Tweak self-armouring" Nick Alcock
2024-12-07 4:37 ` [DTrace-devel] " Kris Van Hees
2024-12-03 11:36 ` [PATCH 2/5] proc: more self-grab improvements Nick Alcock
2024-12-03 13:43 ` Nick Alcock [this message]
2024-12-05 12:58 ` Nick Alcock
2024-12-05 13:43 ` [DTrace-devel] " Nick Alcock
2024-12-07 4:38 ` Kris Van Hees
2024-12-03 11:36 ` [PATCH 3/5] libproc: debugging improvements Nick Alcock
2024-12-07 4:38 ` Kris Van Hees
2024-12-03 11:36 ` [PATCH 4/5] libproc: guard against Puntrace() of terminated processes Nick Alcock
2024-12-03 18:06 ` [DTrace-devel] " Nick Alcock
2024-12-03 18:09 ` Nick Alcock
2024-12-07 4:38 ` Kris Van Hees
2024-12-03 11:36 ` [PATCH 5/5] libproc: drop Pgrab() special cases in Ptrace() Nick Alcock
2024-12-07 4:40 ` 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=87frn43mqq.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.