From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Results of systemtap-20071027 snapshot on i686
Date: Thu, 01 Nov 2007 21:07:00 -0000 [thread overview]
Message-ID: <472A3FFC.4050803@redhat.com> (raw)
Resend this with the proper subject line.
It looks like pr5230 cause a number of the tests to fail. This should
is fixed in the current CVS.
The only the i686 kernel 2.6.24-rc1 currently exercising the kernel markers.
Need to take a closer look to see what is going on with the failures.
rhel4 i686
Date: 200710291549
User: wcohen
Kernel: Linux 2.6.24-rc1 #1 SMP Mon Oct 29 10:27:37 EDT 2007 i686 athlon i386
GNU/Linux
Testsuite summary of failed tests
FAIL: K_MARKER04 compilation failed
FAIL: KM_MARKER02 compilation failed
FAIL: buildok/ioblock_test.stp (pr5231)
FAIL: buildok/nfs-all-probes.stp (pr5150)
FAIL: buildok/syscall.stp (pr5230) fixed in cvs
FAIL: sys.stp (pr5230) fixed in cvs
FAIL: 32-bit access
FAIL: 32-bit acct
FAIL: 32-bit alarm
FAIL: 32-bit chmod
FAIL: 32-bit clock
FAIL: 32-bit dir
FAIL: 32-bit forkwait
FAIL: 32-bit futimes
FAIL: 32-bit itimer
FAIL: 32-bit link
FAIL: 32-bit mmap
FAIL: 32-bit mount
FAIL: 32-bit net1
FAIL: 32-bit openclose
FAIL: 32-bit poll
FAIL: 32-bit readwrite
FAIL: 32-bit rt_signal
FAIL: 32-bit select
FAIL: 32-bit sendfile
FAIL: 32-bit signal
FAIL: 32-bit stat
FAIL: 32-bit statfs
FAIL: 32-bit swap
FAIL: 32-bit sync
FAIL: 32-bit timer
FAIL: 32-bit trunc
FAIL: 32-bit uid
FAIL: 32-bit uid16
FAIL: 32-bit umask
FAIL: 32-bit unlink
=== systemtap Summary ===
# of expected passes 437
# of unexpected failures 36
# of expected failures 152
# of unknown successes 3
# of known failures 3
# of untested testcases 15
# of unsupported tests 1
runtest completed at Mon Oct 29 13:04:23 2007
reply other threads:[~2007-11-01 21:07 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=472A3FFC.4050803@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).