From: Srinivasan Subramanian3 <srinivass@in.ibm.com>
To: systemtap@sourceware.org
Subject: Systemtap Snap:e3851784 test on kernel 2.6.31-rc4-git1
Date: Tue, 28 Jul 2009 12:27:00 -0000 [thread overview]
Message-ID: <OF1C300710.CDC4DECC-ON65257601.00419C1C-65257601.0044626F@in.ibm.com> (raw)
Hello All,
Here is the summary of SystemTap Snap:e3851784 on kernel 2.6.31-rc4-git1.
elfutils version-0.141
Arch: ppc64
=== systemtap Summary ===
# of expected passes 842
# of unexpected failures 33
# of unexpected successes 9
# of expected failures 203
# of unknown successes 2
# of known failures 5
# of untested testcases 166
# of unsupported tests 2
Unexpected Failures
==================
FAIL: backtrace (1 0)
FAIL: backtrace-unwindsyms (1 0)
FAIL: debugpath-bad (eof)
FAIL: gtod (2)
FAIL: systemtap.base/kmodule.stp startup (timeout)
FAIL: K_MARKER23 was cached
FAIL: backtrace of yyy_func2 (1)
FAIL: print_stack of yyy_func2 (1)
FAIL: backtrace of yyy_func3 (1)
FAIL: print_stack of yyy_func3 (1)
FAIL: backtrace of yyy_func4 (1)
FAIL: print_stack of yyy_func4 (1)
FAIL: integer function arguments -- numeric
FAIL: unsigned function arguments -- numeric
FAIL: long function arguments -- numeric
FAIL: int64 function arguments -- numeric
FAIL: char function arguments -- numeric
FAIL: string function arguments -- numeric
FAIL: integer function arguments -- numeric --kelf --ignore-dwarf
FAIL: unsigned function arguments -- numeric --kelf --ignore-dwarf
FAIL: long function arguments -- numeric --kelf --ignore-dwarf
FAIL: int64 function arguments -- numeric --kelf --ignore-dwarf
FAIL: char function arguments -- numeric --kelf --ignore-dwarf
FAIL: string function arguments -- numeric --kelf --ignore-dwarf
FAIL: buildok/signal-all-probes.stp
FAIL: systemtap.printf/bin6.stp
FAIL: 64-bit net1
FAIL: 64-bit readwrite
FAIL: 64-bit signal
FAIL: 32-bit net1
FAIL: 32-bit readwrite
FAIL: 32-bit signal
FAIL: 32-bit statfs
===================================
Thanks &
---------------------------------
Best Regards,
Srinivasan S,
Linux on System z, LTC
srinivass@in.ibm.com
srinivass@linux.vnet.ibm.com
----------------------------------
reply other threads:[~2009-07-28 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=OF1C300710.CDC4DECC-ON65257601.00419C1C-65257601.0044626F@in.ibm.com \
--to=srinivass@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).