From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: Stan Cox <scox@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: test results on ia64, s390, ppc64
Date: Wed, 03 Jun 2009 08:31:00 -0000 [thread overview]
Message-ID: <4A263516.3030703@linux.vnet.ibm.com> (raw)
In-Reply-To: <4A1575A1.8050802@redhat.com>
Hi Stan,
Stan Cox wrote:
> stap version 0.9.7/0.137
>
> ia64
>
> # of expected passes 720
> # of unexpected failures 143 (102 of these are ...with
> server...failures)
> # of unexpected successes 9
> # of expected failures 195
> # of known failures 12
> # of untested testcases 9
> # of unsupported tests 3
>
> FAIL: backtrace (1 0)
> FAIL: backtrace-unwindsyms (1 0)
> FAIL: bz10078 -p4
> FAIL: bz10078 -p5 (0)
> FAIL: bz6850 -p4
> FAIL: bz6850 -p5
> FAIL: crash - crash(8) data
> FAIL: empty-struct resolve-pass was cached
> FAIL: flightrec2 (log file size (3))
> FAIL: itrace1 startup (eof)
> FAIL: itrace2 startup (eof)
> FAIL: itrace3 startup (eof)
> FAIL: systemtap.base/kprobes.stp startup (eof)
> FAIL: labels exe .label 0
> FAIL: sdt "" # no uprobes
> FAIL: sdt c++ ""
> FAIL: sdt additional_flags=-std=gnu89
> FAIL: sdt c++ additional_flags=-std=gnu89
> FAIL: sdt additional_flags=-ansi
> FAIL: sdt c++ additional_flags=-ansi
> FAIL: sdt additional_flags=-pedantic
> FAIL: sdt c++ additional_flags=-pedantic
> FAIL: sdt additional_flags=-ansi additional_flags=-pedantic
> FAIL: sdt c++ additional_flags=-ansi additional_flags=-pedantic
> FAIL: sdt additional_flags=-O2
> FAIL: sdt c++ additional_flags=-O2
> FAIL: sdt additional_flags="-O3"
> FAIL: sdt c++ additional_flags="-O3"
> FAIL: static_uprobes C (0)
> FAIL: tracepoint kernel.trace("rpc_bind_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_connect_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_call_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: systemtap.base/tracepoints.stp
> FAIL: uprobes -p4
> FAIL: uprobes -p5 (0)
> FAIL: systemtap.base/uprobes_lib.stp
> FAIL: systemtap.base/uprobes_uname.stp
> FAIL: uprobes_ustack print (0)
> FAIL: uprobes_ustack main (0)
> FAIL: uprobes_ustack main_func (0)
> FAIL: uprobes_ustack lib_main (0)
> FAIL: uprobes_ustack lib_func (0)
> FAIL: warnings (0)
> FAIL: function arguments -- numeric: compilation failed
> FAIL: function arguments -- numeric --kelf --ignore-dwarf:
> compilation failed
> FAIL: usymbols
> FAIL: semok/nodwf03.stp
>
> s390x
>
> # of expected passes 751
> # of unexpected failures 160 (102 of these are ...with
> server...failures)
> # of unexpected successes 8
> # of expected failures 196
> # of known failures 12
> # of untested testcases 7
> # of unsupported tests 2
>
> FAIL: backtrace (1 0)
> FAIL: backtrace-unwindsyms (1 0)
> FAIL: crash - crash(8) data
> FAIL: flightrec2 (log file numbers (1, 1))
> FAIL: flightrec2 (log file size (2))
> FAIL: itrace1 startup (eof)
> FAIL: itrace2 startup (eof)
> FAIL: itrace3 startup (eof)
> FAIL: systemtap.base/kmodule.stp startup (eof)
> FAIL: systemtap.base/kprobes.stp startup (eof)
> FAIL: labels exe .label 0
> FAIL: sdt "" # user space variables are not accessed
> correctly
> FAIL: sdt c++ "" FAIL: sdt additional_flags=-std=gnu89
> FAIL: sdt c++ additional_flags=-std=gnu89
> FAIL: sdt additional_flags=-ansi
> FAIL: sdt c++ additional_flags=-ansi
> FAIL: sdt additional_flags=-pedantic
> FAIL: sdt c++ additional_flags=-pedantic
> FAIL: sdt additional_flags=-ansi additional_flags=-pedantic
> FAIL: sdt c++ additional_flags=-ansi additional_flags=-pedantic
> FAIL: sdt additional_flags=-O2
> FAIL: sdt c++ additional_flags=-O2
> FAIL: sdt additional_flags="-O3"
> FAIL: sdt c++ additional_flags="-O3"
> FAIL: skip tracking (2 0)
> FAIL: static_uprobes C (0)
> FAIL: stmt_rel line numbers
> FAIL: tracepoint kernel.trace("rpc_bind_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_connect_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_call_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: systemtap.base/tracepoints.stp
> FAIL: uprobes -p5 (0)
> FAIL: systemtap.base/uprobes_lib.stp
> FAIL: systemtap.base/uprobes_uname.stp
> FAIL: uprobes_ustack print (2)
> FAIL: uprobes_ustack main (0)
> FAIL: uprobes_ustack main_func (2)
> FAIL: uprobes_ustack lib_main (0)
> FAIL: uprobes_ustack lib_func (0)
> FAIL: 32_BIT_UTRACE_SYSCALL_ARGS shutdown (eof)
> 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 -- numeric: unexpected timeout
> FAIL: function arguments -- numeric --kelf --ignore-dwarf:
> unexpected timeout
> FAIL: usymbols
> FAIL: buildok/four.stp
> FAIL: buildok/nfsd-all-probes.stp
> FAIL: buildok/scheduler-all-probes.stp
> FAIL: buildok/scsi-all-probes.stp
> FAIL: buildok/scsi.stp
> FAIL: buildok/seventeen.stp
> FAIL: buildok/twentyfive.stp
> FAIL: transok/tval-opt.stp
> FAIL: systemtap.printf/bin6.stp
> FAIL: systemtap.printf/memory1.stp
> FAIL: systemtap.stress/current.stp compilation
> FAIL: 32-bit signal
> FAIL: 32-bit statfs
>
> ppc64
>
> # of expected passes 843
> # of unexpected failures 47
> # of unexpected successes 9
> # of expected failures 195
> # of unknown successes 2
> # of known failures 10
> # of untested testcases 14
> # of unsupported tests 2
>
> FAIL: backtrace (1 0)
> FAIL: backtrace-unwindsyms (1 0)
> FAIL: systemtap.base/cast.stp
> FAIL: crash - crash(8) data
> FAIL: flightrec2 (log file size (3))
> FAIL: gtod (39)
> FAIL: itrace1 startup (eof)
> FAIL: itrace2 startup (eof)
> FAIL: itrace3 startup (eof)
> FAIL: systemtap.base/kprobes.stp startup (eof)
> FAIL: compiling sdt.c "" # does not include mjw's nop patch
> FAIL: compiling sdt.c additional_flags=-std=gnu89
> FAIL: compiling sdt.c additional_flags=-ansi
> FAIL: compiling sdt.c additional_flags=-pedantic
> FAIL: compiling sdt.c additional_flags=-ansi
> additional_flags=-pedantic
> FAIL: compiling sdt.c additional_flags=-O2
> FAIL: compiling sdt.c additional_flags="-O3"
> FAIL: static_uprobes compiling C -g
> FAIL: tracepoint kernel.trace("rpc_connect_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_call_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: tracepoint kernel.trace("rpc_bind_status") -p4 Pass 4:
> compilation failed. Try again with another '--vp 0001' option.
> FAIL: systemtap.base/tracepoints.stp
> FAIL: systemtap.base/uprobes_uname.stp
> FAIL: uprobes_ustack print (1)
> FAIL: uprobes_ustack main (0)
> FAIL: uprobes_ustack main_func (1)
> FAIL: uprobes_ustack lib_main (0)
> FAIL: uprobes_ustack lib_func (0)
> 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: function arguments -- numeric: unexpected timeout
> FAIL: function arguments -- numeric --kelf --ignore-dwarf:
> unexpected timeout
> FAIL: usymbols
> FAIL: buildok/uaddr.stp
> FAIL: buildok/vfs_testcase.stp
> FAIL: systemtap.printf/bin6.stp
> FAIL: 64-bit readwrite
> FAIL: 64-bit signal
> FAIL: 32-bit readwrite
> FAIL: 32-bit signal
> FAIL: 32-bit statfs
>
Were these tests run on a RHEL-5.x system ? Could you pls indicate the
kernel version ?
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
prev parent reply other threads:[~2009-06-03 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 15:39 Stan Cox
2009-05-22 5:54 ` Ananth N Mavinakayanahalli
2009-06-03 8:31 ` Prerna Saxena [this message]
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=4A263516.3030703@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.com \
--cc=scox@redhat.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).