public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Hien Nguyen <hien@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Testsuite run on ppc64
Date: Thu, 03 Nov 2005 21:10:00 -0000	[thread overview]
Message-ID: <436A7C85.3020509@redhat.com> (raw)
In-Reply-To: <436A7305.6030509@us.ibm.com>

Hien, Thanks for running the the tests on PPC64. The systemtap.log won't 
give the details on the compilation failure, stap hides thoes details. 
Could you do the following?

For systemtap.base/kmodule.stp:

1) stap -V -k  ./systemtap.base/kmodule.stp compilation >& error.txt
2) post the error.txt and a tarball of the generated kernel module

For ./systemtap.samples/symbols.exp it looks like it only matched one 
line. Maybe modify the ./systemtap.samples/symbols.exp like the 
following to find out which line it is matching on. It looks like the 
regular expression needs to be corrected.

set test "symbols"

spawn stap -g ./$subdir/symbols.stp
set ok 0
expect {
     -timeout 30
     -re { 0x[a-f0-9]+.*\r} { incr ok; pass "$test matches"; exp_continue; }
     timeout { fail "$test (timeout)" }
     eof { }
}

It is odd that the results for the automated run of syscall1.stp and 
syscall2.stp differ from running by hand.

-Will

Hien Nguyen wrote:
> Here's the testsuite result for ppc64. There are 4 failed tests listed 
> below and my comments:
> 
> 1)  FAIL: ./systemtap.base/kmodule.stp compilation  -
> probably because the test could not find stap_run
> 
> 2) Running ./systemtap.samples/symbols.exp ...
> FAIL: symbols (1)
> 
> If I run the "stap symbols", I could count 11 line, looks like the test 
> looks for 11 count but some how it still failed
> # stap symbols.stp
> 0x0
> 0x80000000
> 0xc0000000
> 0xe0000000
> 0xf0000000
> 0xffffffff
> 0xffffffff00000000 : .xfrm6_state_fini+0x2ffffffeffc7a65c/0x0 [ipv6]
> 0xffffffff80000000 : .xfrm6_state_fini+0x2fffffff7fc7a65c/0x0 [ipv6]
> 0xffffffff80120000 : .xfrm6_state_fini+0x2fffffff7fd9a65c/0x0 [ipv6]
> 0xffffffff88000000 : .xfrm6_state_fini+0x2fffffff87c7a65c/0x0 [ipv6]
> 0xffffffffffffffff : .xfrm6_state_fini+0x2fffffffffc7a65b/0x0 [ipv6]
> 
> 3) Running ./systemtap.samples/syscalls1.exp ...
> FAIL: syscalls-count (24)
> 
> The test looks for 250-300 system calls, but I run the below and it 
> seems to give the correct value
> # stap -p2 syscalls.stp | wc -l
> 290
> 
> 
> 4) Running ./systemtap.samples/syscalls2.exp ...
> FAIL: syscalls-run (4)
> 
> The  looks for 100-150 count, run the below and it seems to give the 
> correct value.
> # stap syscalls.stp | wc -l
> 101
> 
> 
> ------ Test suite result starts here -----
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file 
> for target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for 
> target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./systemtap/systemtap-run.exp ...
> Running ./systemtap.base/add.exp ...
> Running ./systemtap.base/and.exp ...
> Running ./systemtap.base/dec.exp ...
> Running ./systemtap.base/div.exp ...
> Running ./systemtap.base/div0.exp ...
> Running ./systemtap.base/equal.exp ...
> Running ./systemtap.base/finloop2.exp ...
> Running ./systemtap.base/gt.exp ...
> Running ./systemtap.base/gte.exp ...
> Running ./systemtap.base/if.exp ...
> Running ./systemtap.base/inc.exp ...
> Running ./systemtap.base/kfunct.exp ...
> Running ./systemtap.base/kmodule.exp ...
> FAIL: ./systemtap.base/kmodule.stp compilation
> Running ./systemtap.base/logical_and.exp ...
> Running ./systemtap.base/logical_not.exp ...
> Running ./systemtap.base/logical_or.exp ...
> Running ./systemtap.base/lshift.exp ...
> Running ./systemtap.base/lt.exp ...
> Running ./systemtap.base/lte.exp ...
> Running ./systemtap.base/mod.exp ...
> Running ./systemtap.base/mult.exp ...
> Running ./systemtap.base/ne.exp ...
> Running ./systemtap.base/neg.exp ...
> Running ./systemtap.base/not.exp ...
> Running ./systemtap.base/or.exp ...
> Running ./systemtap.base/rshift.exp ...
> Running ./systemtap.base/simple.exp ...
> Running ./systemtap.base/subtract.exp ...
> Running ./systemtap.base/tri.exp ...
> Running ./systemtap.base/xor.exp ...
> Running ./systemtap.samples/arith.exp ...
> Running ./systemtap.samples/arith_limits.exp ...
> Running ./systemtap.samples/control_limits.exp ...
> Running ./systemtap.samples/pfaults.exp ...
> Running ./systemtap.samples/primes.exp ...
> Running ./systemtap.samples/profile.exp ...
> Running ./systemtap.samples/symbols.exp ...
> FAIL: symbols (1)
> Running ./systemtap.samples/syscalls1.exp ...
> FAIL: syscalls-count (24)
> Running ./systemtap.samples/syscalls2.exp ...
> FAIL: syscalls-run (4)
> Running ./systemtap.samples/sysopen.exp ...
> Running ./systemtap.samples/transport.exp ...
> 
>                ===  Summary ===
> 
> # of expected passes            101
> # of unexpected failures        4
> 

  reply	other threads:[~2005-11-03 21:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 20:29 Hien Nguyen
2005-11-03 21:10 ` William Cohen [this message]
2005-11-03 21:56   ` Frank Ch. Eigler
2005-11-03 22:07     ` Hien Nguyen
2005-11-03 23:52       ` William Cohen
2005-11-04 17:27         ` Hien Nguyen
2005-11-04 17:58           ` William Cohen
2005-11-03 22:25   ` Hien Nguyen

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=436A7C85.3020509@redhat.com \
    --to=wcohen@redhat.com \
    --cc=hien@us.ibm.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).