From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Results of systemtap-20071020 snapshot on ia64
Date: Tue, 23 Oct 2007 18:35:00 -0000 [thread overview]
Message-ID: <471E3EF5.6020609@redhat.com> (raw)
RHEL4 ia64
Date: 200710221308
User: wcohen
Kernel: Linux 2.6.23 #1 SMP Thu Oct 11 11:41:53 EDT 2007 ia64 ia64 ia64 GNU/Linux
Testsuite summary of failed tests
FAIL: backtrace of yyy_func4.return (3) pr5051
FAIL: print_stack of yyy_func4.return (1) pr5051
FAIL: buildok/nfs-all-probes.stp pr5150
FAIL: buildok/rpc-all-probes.stp pr5151
FAIL: buildok/scheduler-all-probes.stp pr5152
FAIL: buildok/signal-all-probes.stp pr1155
FAIL: proc_snoop.stp pr1155
FAIL: systemtap.samples/ioblocktest.stp shutdown (eof)
FAIL: systemtap.stress/current.stp startup (eof)
FAIL: 64-bit acct pr4475, pr4915?
FAIL: 64-bit alarm pr4475, pr4915?
FAIL: 64-bit chmod pr4475, pr4915?
FAIL: 64-bit dir pr4475, pr4915?
FAIL: 64-bit forkwait pr4475, pr4915?
FAIL: 64-bit mmap pr4475, pr4915?
FAIL: 64-bit mount pr4475, pr4915?
FAIL: 64-bit net1 pr4475, pr4915?
FAIL: 64-bit openclose pr4475, pr4915?
FAIL: 64-bit readwrite pr4475, pr4915?
FAIL: 64-bit rt_signal pr4475, pr4915?
FAIL: 64-bit signal pr4475, pr4915?
FAIL: 64-bit stat pr4475, pr4915?
FAIL: 64-bit statfs pr4475, pr4915?
=== systemtap Summary ===
# of expected passes 426
# of unexpected failures 23
# of expected failures 152
# of unknown successes 1
# of known failures 5
# of untested testcases 26
# of unsupported tests 2
runtest completed at Mon Oct 22 12:23:13 2007
next reply other threads:[~2007-10-23 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 18:35 William Cohen [this message]
2007-11-01 19:26 William Cohen
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=471E3EF5.6020609@redhat.com \
--to=wcohen@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).