testsuite summary report - s390x

[David Smith <dsmith at redhat dot com>]

I just finished analyzing the full testsuite results on s390x.  I've
attached the
'sum' file (and sent it to dejazilla).  Here are the highlights.


Host: 2.6.18-194.el5 #1 SMP
Snapshot: version 1.2/0.141 non-git sources
GCC: 4.1.2 [gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)]
Distro: Red Hat Enterprise Linux Server release 5.5 (Tikanga)

                === systemtap Summary ===

# of expected passes            1414
# of unexpected failures        244
# of unexpected successes       8
# of expected failures          232
# of unknown successes          1
# of known failures             9
# of untested testcases         27
# of unsupported tests          4

244 failures sound like a lot, but like the ppc results I posted
recently, 160 of those failures come from 1 test -
systemtap.exelib/exelib.exp.  Here is the list of the remaining failures
with some comments:

FAIL: atomic1 didn't receive expected error
FAIL: atomic3 didn't receive expected error
FAIL: atomic5 didn't receive expected error
FAIL: atomic7 didn't receive expected error

The above failures are because s390x doesn't give an error when reading
0 (and similar bad addresses).

FAIL: cxxclass

The above is from systemtap.base/cxxclass.exp.  It got the following error:

ERROR: kernel read fault at 0x000003ffff9aae58 (addr) near identifier
'$arg1' at /root/src/testsuite/systemtap.base/cxxclass.stp:13:24

I'm unsure of why this is happening.

FAIL: externalvar

I've filed PR11751 against this.

FAIL: flightrec1 (failed to switch output file)
FAIL: flightrec4 (failed to switch output file)

Both of the above failures don't happen when the tests
(systemtap.base/flightrec[14].exp) are run by themselves.  I believe the
testcases have a timing problem.

FAIL: inlinedvars--O0
FAIL: inlinedvars--O1
FAIL: inlinedvars--O2
FAIL: inlinedvars--O3

These are from systemtap.base/inlinedvars.exp.  The errors look similar
to the cxxclass.exp errors:

ERROR: kernel read fault at 0x000003ffffa47298 (addr) near identifier
'$p_name' at /root/src/testsuite/systemtap.base/inlinedvars.stp:3:38

FAIL: itrace_single2 shutdown (eof)

s390x doesn't have block stepping, and single stepping got an error.

FAIL: labels exe .label 0

Like others, the above failed with:

ERROR: kernel read fault at 0x000003ffff866400 (addr) near identifier
'$$vars' at /root/s390x/testsuite/labels.stp:2:90

FAIL: systemtap.base/pointer_array.stp

Like some earlier tests, this one is failing with:

ERROR: kernel read fault at 0x00000000800120a0 (addr) near identifier
'$argv' at /root/src/testsuite/systemtap.base/pointer_array.stp:4:29

FAIL: sdt "" uprobe
FAIL: sdt c++ "" uprobe
FAIL: sdt additional_flags=-std=gnu89 uprobe
FAIL: sdt c++ additional_flags=-std=gnu89 uprobe
FAIL: sdt additional_flags=-ansi uprobe
FAIL: sdt c++ additional_flags=-ansi uprobe
FAIL: sdt additional_flags=-pedantic uprobe
FAIL: sdt c++ additional_flags=-pedantic uprobe
FAIL: sdt additional_flags=-ansi additional_flags=-pedantic uprobe
FAIL: sdt c++ additional_flags=-ansi additional_flags=-pedantic uprobe
FAIL: sdt additional_flags=-O2 uprobe
FAIL: sdt c++ additional_flags=-O2 uprobe
FAIL: sdt additional_flags="-O3" uprobe
FAIL: sdt c++ additional_flags="-O3" uprobe
FAIL: sdt_misc (0) uprobe
FAIL: sdt_misc (0) uprobe attach
FAIL: sdt_misc (0) shared uprobe
FAIL: sdt_misc (0) uprobe shared attach
FAIL: sdt_misc (0) uprobe --types
FAIL: sdt_misc (0) kprobe --types
FAIL: sdt_misc compiling V2
FAIL: stmt_rel line numbers

sdt failures...

FAIL: uprobes -p5 (0)

Like others, the above fails with:

ERROR: kernel read fault at 0x000003fffff0341c (addr) near identifier
'$$parms' at /root/src/testsuite/systemtap.base/uprobes.stp:2:73

FAIL: 32_BIT_UTRACE_SYSCALL_ARGS shutdown (eof)

The above error happens because systemtap can't decode mmap()'s
arguments when run on a 31-bit executable (it works fine on a 64-bit
executable).  Since strace also can't deocde those arguments correctly,
I'm going to ignore this one.

FAIL: warnings (0)

This is a testcase problem.  The warnings.exp testcase fails with:

semantic error: no match while resolving probe point
kernel.statement("bio_init@fs/bio.c+5")

On s390x, the optimizer has really compressed that function.  If I
change it to 'kernel.statement("bio_init@fs/bio.c+1")' the test passes fine.

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: fib (2 0)
FAIL: fib (10 0)

All of the above are backtrace problems.  Basically the backtraces
aren't correct:

--- yyy_func4 ---
the stack is 0x0000000020b1403c 0x0000000000000000 0x0000000000000000
0x00000000001a286e 0x000000000010e878 0x000000000010e878
 0x0000000020b1403c : yyy_func4+0x0/0xc [systemtap_test_module2]
 0x0000000000000000 : __mod_license91+0x0/0xc [systemtap_test_module2]
 0x0000000000000000 : __mod_license91+0x0/0xc [systemtap_test_module2]
 0x00000000001a286e
 0x000000000010e878
 0x000000000010e878

yyy_func4 should show yyy_func[321] above it on the stack.

FAIL: systemtap.examples/general/badname build
FAIL: systemtap.examples/general/badname run
FAIL: systemtap.examples/general/graphs build
FAIL: systemtap.examples/general/graphs run
FAIL: systemtap.examples/process/chng_cpu build
FAIL: systemtap.examples/process/chng_cpu run

I believe these are problems with inline function args.

FAIL: buildok/pr10678.stp

This one fails because the ne2k_pci module doesn't exist.

FAIL: buildok/process_test.stp

This is a problem with inline function args.

FAIL: semok/thirtynine.stp

This is a problem with inline function args.

FAIL: semok/thirtysix.stp

The semok/thirtysix.stp failure is very odd.  This one is failing on the
following line:

probe kernel.mark("*")? { println(@defined($name)?$name:$nosuchvar) } #
valid

What's odd is that this kernel has kernel.mark probes and $name is
supposed to be defined for all kernel.mark probes.

FAIL: systemtap.printf/memory1.stp

Like many other tests, the above test fails with:

ERROR: kernel read fault at 0x000002aaaab5f440 (_addr) near identifier
'$filename' at /usr/local/share/systemtap/tapset/syscalls2.stp:125:25

FAIL: buildok/memory-mmap.stp with server
FAIL: buildok/nfs-fop.check_flags.stp with server
FAIL: buildok/pr10678.stp with server
FAIL: buildok/process_test.stp with server
FAIL: buildok/scheduler-ctxswitch.stp with server
FAIL: buildok/scheduler-migrate.stp with server
FAIL: buildok/signal-handle.stp with server
FAIL: buildok/thirtythree.stp with server
FAIL: buildok/tty-resize.stp with server

FAIL: systemtap.stress/current.stp compilation

current.exp failed with:

semantic error: no match while resolving probe point
kernel.function("__switch_to").call
semantic error: no match while resolving probe point
kernel.function("__switch_to").return

I'll look into this one more.

FAIL: 64-bit alarm nd_syscall
FAIL: 64-bit clock nd_syscall
FAIL: 64-bit forkwait nd_syscall
FAIL: 64-bit inotify nd_syscall
FAIL: 64-bit mmap nd_syscall
FAIL: 64-bit select nd_syscall
FAIL: 32-bit access nd_syscall
FAIL: 32-bit alarm nd_syscall
FAIL: 32-bit clock nd_syscall
FAIL: 32-bit forkwait nd_syscall
FAIL: 32-bit inotify nd_syscall
FAIL: 32-bit link nd_syscall
FAIL: 32-bit mmap nd_syscall
FAIL: 32-bit select nd_syscall
FAIL: 32-bit signal nd_syscall

These are failing because of 2 main reasons.

1) The testcase keeps getting errors of "ERROR: Cannot access arg(6)" on
syscalls that don't have 6 args.

2) Compile errors, like:

/root/src/testsuite/systemtap.syscall/eventfd.c:2:25: error:
sys/eventfd.h: No such file or directory

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

Attachment: systemtap.sum
Description: Text document