From: Mark Wielaard <mjw@redhat.com>
To: ananth@in.ibm.com
Cc: Pavan Naregundi <pavan.naregundi@in.ibm.com>, systemtap@sourceware.org
Subject: Re: Systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
Date: Wed, 29 Apr 2009 08:57:00 -0000 [thread overview]
Message-ID: <1240995422.2389.2.camel@fedora.wildebeest.org> (raw)
In-Reply-To: <20090428065617.GD1531@in.ibm.com>
On Tue, 2009-04-28 at 12:26 +0530, Ananth N Mavinakayanahalli wrote:
> On Mon, Apr 27, 2009 at 04:42:50PM +0200, Mark Wielaard wrote:
> > On Mon, 2009-04-27 at 17:17 +0530, Pavan Naregundi wrote:
> > > Results of systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
> > > Arch: ppc64
> > >
> > > FAIL: LOCAL1 (0)
>
> I've seen the above fail with LOCAL1 (2), which actually needs to be
> flagged as a success. I guess the issue is with checking of rc -- down
> in alternatives.exp:
>
> - if {$rc == 1} { pass $test } else { fail "$test ($rc)" }
> + if {$rc >= 1} { pass $test } else { fail "$test ($rc)" }
>
> should fix the problem.
Yes, that seems fine. The LOCAL1 (0) failure case is as you observed
because of the syscall wrappers issue (I am thinking about the patch you
proposed in PR10007 and testing it locally - x86_64 only for now
though).
Cheers,
Mark
next prev parent reply other threads:[~2009-04-29 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 11:49 Pavan Naregundi
2009-04-27 14:43 ` Mark Wielaard
2009-04-28 5:11 ` Pavan Naregundi
2009-04-28 6:02 ` Pavan Naregundi
2009-04-28 6:07 ` Ananth N Mavinakayanahalli
2009-04-29 9:37 ` Mark Wielaard
2009-04-29 19:01 ` Josh Stone
2009-04-29 9:41 ` Mark Wielaard
2009-04-28 6:56 ` Ananth N Mavinakayanahalli
2009-04-29 8:57 ` Mark Wielaard [this message]
2009-04-29 9:26 ` Ananth N Mavinakayanahalli
2009-04-29 12:08 ` Mark Wielaard
2009-04-29 12:21 ` Ananth N Mavinakayanahalli
2009-04-29 12:27 ` Mark Wielaard
2009-04-29 13:15 ` David Smith
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=1240995422.2389.2.camel@fedora.wildebeest.org \
--to=mjw@redhat.com \
--cc=ananth@in.ibm.com \
--cc=pavan.naregundi@in.ibm.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).