public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Martin Hunt <hunt@redhat.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: Recent test results
Date: Fri, 11 Nov 2005 20:53:00 -0000	[thread overview]
Message-ID: <437504AE.8000503@redhat.com> (raw)
In-Reply-To: <1131741388.3899.2.camel@monkey2>

Martin Hunt wrote:
> On Fri, 2005-11-11 at 14:35 -0500, William Cohen wrote:
> 
>>Tried out testing a current snapshot of systemtap (20051111) on some
>>systems.
> 
> [...]
> 
>>Looking into why some of the x86_64 tests start failing when all are
>>run. It looks like it is failing in the same way as the ia64 tests
>>that Anil ran earlier in the week; things go wrong with simple.exp.
>>Also noticed that x86_64 version failed to report the systemtap
>>version.
> 
> I got the same results as you.
> 
> I'm certainly not an expect expert, but a quick look at stap_run.exp
> shows a major flaw. I made a quick fix and now I get:
> 
> Running ./systemtap.samples/syscalls2.exp ...
> Running ./systemtap.samples/sysopen.exp ...
> Running ./systemtap.samples/transport.exp ...
> 
>                 === systemtap Summary ===
> 
> # of expected passes            107
> 
> kernel version: 2.6.9-22.0.1.ELsmp
> systemtap translator version: version 0.4.2 built 2005-11-11
> 
> 
> 

Thanks, Martin.

I am wondering if there are similar close operations missing in test run 
later in the sequence.


-Will

  reply	other threads:[~2005-11-11 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 19:36 William Cohen
2005-11-11 20:38 ` Martin Hunt
2005-11-11 20:53   ` William Cohen [this message]
2005-11-11 21:23     ` Martin Hunt
2005-11-11 20:50 Keshavamurthy, Anil S
2005-11-11 20:51 ` William Cohen
2005-11-11 21:14   ` Keshavamurthy Anil S
2005-11-11 20:52 ` Martin Hunt
2005-11-14  3:42 Mao, Bibo
2005-11-17 18:04 Keshavamurthy, Anil S

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=437504AE.8000503@redhat.com \
    --to=wcohen@redhat.com \
    --cc=hunt@redhat.com \
    --cc=systemtap@sources.redhat.com \
    /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).