From: Maran <maranp@linux.vnet.ibm.com>
To: systemtap@sourceware.org
Subject: systemtap testsuite summary report - s390x
Date: Tue, 13 Oct 2009 08:05:00 -0000 [thread overview]
Message-ID: <4AD434C6.1050601@linux.vnet.ibm.com> (raw)
SystemTap translator/driver (version 1.0/0.142 commit
release-1.0-82-g9a59aed)
Arch : s390x
Kernel version : 2.6.32-rc3
Distro : RHEL 5.4
=== systemtap Summary ===
# of expected passes 735
# of unexpected failures 57
# of unexpected successes 8
# of expected failures 205
# of unknown successes 1
# of known failures 6
# of untested testcases 156
# of unsupported tests 4
Unexpected failures
==================
FAIL: cmd_parse1: unexpected EOF
FAIL: cmd_parse2: unexpected EOF
FAIL: cmd_parse3: unexpected EOF
FAIL: cmd_parse4: unexpected EOF
FAIL: cmd_parse5: unexpected EOF
FAIL: cmd_parse6: unexpected EOF
FAIL: cmd_parse7: unexpected EOF
FAIL: cmd_parse16: eof
FAIL: debugpath-good (eof)
FAIL: empty-struct resolve-pass compilation failed
FAIL: gtod (100)
FAIL: systemtap.base/pointer_array.stp
FAIL: preprocessor basic ops
FAIL: prologues -P
FAIL: skip tracking (2 0)
FAIL: bz6905 -p2 (1)
FAIL: bz10294 -p2 (1)
FAIL: stmtnofunc
FAIL: warnings (0)
FAIL: backtrace of yyy_func2 (2)
FAIL: print_stack of yyy_func2 (2)
FAIL: backtrace of yyy_func3 (2)
FAIL: print_stack of yyy_func3 (2)
FAIL: backtrace of yyy_func4 (2)
FAIL: print_stack of yyy_func4 (2)
FAIL: function arguments: unexpected timeout
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: 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: systemtap.examples/general/badname build
FAIL: systemtap.examples/general/badname run
FAIL: systemtap.examples/profiling/sched_switch build
FAIL: systemtap.examples/profiling/sched_switch run
FAIL: buildok/eighteen.stp
FAIL: buildok/nfsd-all-probes.stp
FAIL: buildok/pr10678.stp
FAIL: buildok/scheduler-all-probes.stp
FAIL: buildok/scheduler-test-tracepoints.stp
FAIL: buildok/seventeen.stp
FAIL: semok/twentyseven.stp
FAIL: semok/utrace01.stp
FAIL: transok/tval-opt.stp
FAIL: systemtap.printf/bin6.stp
FAIL: systemtap.printf/memory1.stp
FAIL: systemtap.stress/current.stp compilation
FAIL: 64-bit acct
FAIL: 64-bit net1
FAIL: 32-bit acct
FAIL: 32-bit net1
FAIL: 32-bit signal
Regards,
Maran
next reply other threads:[~2009-10-13 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 8:05 Maran [this message]
2009-10-13 14:14 ` David Smith
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 6:40 Maran
2009-09-30 9:49 Maran
2009-09-18 5:43 Maran
2009-09-15 7:04 Maran
2009-09-09 10:48 Maran
2009-08-25 5:15 Maran
2009-08-25 7:15 ` Mark Wielaard
2009-08-25 11:14 ` Maran
2009-08-25 11:32 ` Mark Wielaard
2009-08-25 12:11 ` Maran
2009-08-25 12:29 ` Mark Wielaard
2009-07-30 9:59 Maran
2009-07-30 10:03 ` Maran
2009-07-23 7:04 Maran
2009-07-14 13:49 Maran
2009-07-07 6:31 Maran
2009-07-02 6:22 Maran
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=4AD434C6.1050601@linux.vnet.ibm.com \
--to=maranp@linux.vnet.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).