From: David Wilder <dwilder@us.ibm.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Results of systemtap-20071020 snapshot on s390x
Date: Tue, 23 Oct 2007 22:32:00 -0000 [thread overview]
Message-ID: <471E7670.6030500@us.ibm.com> (raw)
uname -r = 2.6.23-rc9
=== systemtap Summary ===
# of expected passes 465
# of unexpected failures 14
# of expected failures 152
# of unknown successes 1
# of known failures 5
# of untested testcases 26
# of unsupported tests 2
FAIL: backtrace of yyy_func3 (2) (PR 4794)
FAIL: print_stack of yyy_func3 (2) (PR 4794)
FAIL: backtrace of yyy_func4.return (3) (PR 4794)
FAIL: print_stack of yyy_func4.return (2) (PR 4794)
FAIL: buildok/nfs-all-probes.stp
FAIL: buildok/rpc-all-probes.stp
FAIL: buildok/scheduler-all-probes.stp
FAIL: buildok/signal-all-probes.stp
FAIL: key.stp
FAIL: keyhack.stp
FAIL: proc_snoop.stp
FAIL: systemtap.stress/current.stp compilation (PR4902)
FAIL: 32-bit rt_signal
FAIL: 32-bit signal
reply other threads:[~2007-10-23 22:32 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=471E7670.6030500@us.ibm.com \
--to=dwilder@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).