Linux DTrace development list
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Sam James <sam@gentoo.org>, dtrace@lists.linux.dev
Subject: Re: [PATCH 3/3] test: fix exit code in tst.newprobes.sh
Date: Sat, 12 Oct 2024 00:13:33 -0400	[thread overview]
Message-ID: <Zwn3bTM5yDP/zGOY@oracle.com> (raw)
In-Reply-To: <a509486a-47d9-5dfa-ad54-5a91bec6169c@oracle.com>

On Fri, Oct 11, 2024 at 11:55:33PM -0400, Eugene Loh wrote:
> Maybe I am a few patches behind.  I thought this test used pid*:awk:: and
> was therefore XFAIL.  I do not object to the patch, but I was only curious
> if we wanted a "real fix" to the test. There are other cases where tests
> have multiple problems and we do not generally seem to settle for fixing
> only one of the problems. Again, though, I'm okay with the patch... it's an
> improvement over what's there.

In general, yes, when we encounter a case like this we tend to fix other more
fundamental problems with the test.  In this case, since it is part of a larger
series of test clean up work, I took it as-is so as to not delay the cleanup
any longer.  But yes, the test will still need extra work to ensure it is
actually correct in terms of functionality.

> On 10/11/24 23:29, Kris Van Hees wrote:
> > On Tue, Aug 20, 2024 at 01:10:22AM +0100, Sam James wrote:
> > > $status is never assigned, just use $?.
> > Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
> > 
> > ... and committed with Signed-off-by added.
> > 
> > > ---
> > >   test/unittest/pid/tst.newprobes.sh | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/test/unittest/pid/tst.newprobes.sh b/test/unittest/pid/tst.newprobes.sh
> > > index a4944688..0980d3b3 100755
> > > --- a/test/unittest/pid/tst.newprobes.sh
> > > +++ b/test/unittest/pid/tst.newprobes.sh
> > > @@ -44,4 +44,4 @@ tick-1s
> > >   }
> > >   EOF
> > > -exit $status
> > > +exit $?
> > > -- 
> > > 2.46.0
> > > 

      reply	other threads:[~2024-10-12  4:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  0:10 [PATCH 0/3] Test exit code fixlets Sam James
2024-08-20  0:10 ` [PATCH 1/3] test: fix exit code in tst.ipv4remotetcp.sh Sam James
2024-10-12  3:29   ` Kris Van Hees
2024-08-20  0:10 ` [PATCH 2/3] test: fix exit code typo in tst.core.sh Sam James
2024-10-12  3:29   ` Kris Van Hees
2024-08-20  0:10 ` [PATCH 3/3] test: fix exit code in tst.newprobes.sh Sam James
2024-08-20  2:14   ` Eugene Loh
2024-10-12  3:29   ` Kris Van Hees
2024-10-12  3:55     ` Eugene Loh
2024-10-12  4:13       ` Kris Van Hees [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=Zwn3bTM5yDP/zGOY@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=eugene.loh@oracle.com \
    --cc=sam@gentoo.org \
    /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