From: Nick Alcock <nick.alcock@oracle.com>
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH 2/5] proc: more self-grab improvements
Date: Thu, 05 Dec 2024 13:43:57 +0000 [thread overview]
Message-ID: <87cyi6p7mq.fsf@esperi.org.uk> (raw)
In-Reply-To: <878qsus2uv.fsf@esperi.org.uk> (Nick Alcock via DTrace-devel's message of "Thu, 05 Dec 2024 12:58:48 +0000")
On 5 Dec 2024, Nick Alcock via DTrace-devel spake thusly:
> Even proc/tst.signals.sh seems to be consistently passing now,
> and that's another unstable-marked nasty test I hadn't got round to
> looking at in ever so long...
Never mind: if this one fails once, it starts XFAILing for every
subsequent run, with different failures every time, and seemingly never
passes again. Very strange, given the lack of any way for the process to
pass state between runs (it doesn't rely on dtprobed or anything). Needs
more debugging after all.
--
NULL && (void)
next prev parent reply other threads:[~2024-12-05 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
2024-12-05 12:58 ` Nick Alcock
2024-12-05 13:43 ` Nick Alcock [this message]
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=87cyi6p7mq.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