Re: [DTrace-devel] [PATCH v2 6/8] test: Check dtrace return status in USDT tst.forker.sh

[Sam James <sam@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]

Kris Van Hees via DTrace-devel <dtrace-devel@oss.oracle.com> writes:

> On Thu, Jun 27, 2024 at 01:25:16AM -0400, eugene.loh@oracle.com wrote:
>> From: Eugene Loh <eugene.loh@oracle.com>
>> 
>> This test was spuriously passing.  DTrace failed to run -- many error
>> messages in the log file indicated as much -- and yet the test passed.
>> 
>> Check the dtrace return status.
>> 
>> The test will pass once USDT supports wildcard provider names.
>> 
>> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
>
> Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

This made me go looking for other issues and I sent a small series for
the obvious ones.

There are other issues around:
* dtrace .. | awk, exit $? wrt no lastpipe, and
* multiple checks but we only exit $? only at the end (this is
debatable)
* exiting 0 at the end when checking for intended failure (perhaps
should do exit 1 if any of them *don't* fai;, see previous point) in a
handful of tests
* tests like test/unittest/udp/tst.ipv6localudp.sh where, while we
normally rely on the implicit exit code being the last command run,
because we do e.g. kill after, we end up not checking it.

Some of this doesn't matter *that* much because of the actual test
output being checked in .r files, but failing faster is nicer for
debugging as well, and in some cases, there is no .r (like this one).

> [...]

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]