From: Josh Stone <jistone@redhat.com>
To: Mark Wielaard <mjw@redhat.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 19:01:00 -0000 [thread overview]
Message-ID: <49F8A3E5.2080606@redhat.com> (raw)
In-Reply-To: <1240997799.2389.5.camel@fedora.wildebeest.org>
Mark Wielaard wrote:
> On Tue, 2009-04-28 at 11:30 +0530, Pavan Naregundi wrote:
>> Running /home/pavan/systemtap/src/testsuite/systemtap.base/cast.exp ...
>> executing: stap /home/pavan/systemtap/src/testsuite/systemtap.base/cast.stp
>> -g
>> FAIL: systemtap.base/cast.stp
>> line 4: expected "tv_sec OK"
>> Got "tv_sec 42 != 0"
>> testcase /home/pavan/systemtap/src/testsuite/systemtap.base/cast.exp
>> completed in 8 seconds
>
> That is strange, maybe struct timeval is different on ppc64 from what we
> expect in the @cast or get_timeval() in the script. Maybe Josh has a
> hunch what is going on (he wrote the test originally).
The scenario where this would fail is a big-endian machine where the
size of "long tv_sec" is different between kernel and user mode. AFAIK,
ppc64 is one such machine.
I would say that the @cast is working fine here -- it's just a bad
assumption on my part in writing the test. I'll see if there's another
struct type I can use that will be more robust...
Josh
next prev parent reply other threads:[~2009-04-29 19:01 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 [this message]
2009-04-29 9:41 ` Mark Wielaard
2009-04-28 6:56 ` Ananth N Mavinakayanahalli
2009-04-29 8:57 ` Mark Wielaard
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=49F8A3E5.2080606@redhat.com \
--to=jistone@redhat.com \
--cc=mjw@redhat.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).