This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Some make installcheck results 2.6.29-0.258.rc8.git2.fc11.i586/0.9/0.140 commit e1e3ba36


Some more make installcheck results.
Unfortunately these look not that good, although some of that is setup
errors, and lots of failures because of one particular kernel read
fault.

Host: Linux rawhide 2.6.29-0.258.rc8.git2.fc11.i586 #1 SMP Mon Mar 16 20:53:59 EDT 2009 i686 i686 i386 GNU/Linux
Snapshot: version 0.9/0.140 commit e1e3ba36
Distro: Fedora release 10.92 (Rawhide)

# of expected passes            632
# of unexpected failures        151
# of unexpected successes       8
# of expected failures          202
# of unknown successes          1
# of known failures             13
# of untested testcases         4

I haven't gone through all of them in detail like in the previous lists.

More than half of the failures (87) probable come from some
misconfiguration with regard to the stap server (it would be nice if the
testsuite gave some hint of what to do to make it work correctly,
because I always forget...)

Then there are lots (30) syscall failures. Most of them fail as follows:

ERROR: kernel read fault at 0x008ef5da (addr) near identifier '$ctx_id'
at /usr/local/systemtap/share/systemtap/tapset/syscalls.stp:1979:11

ERROR: kernel int copy fault at 0xffffffff near identifier 'kernel_int'
at /usr/local/systemtap/share/systemtap/tapset/conversions.stp:44:10

BTW. I noticed that a couple of examples also fail, but still seem to
PASS, like:

attempting command  stap traceio.stp -c "sleep 1"
OUT ERROR: kernel read fault at 0x00002004 (addr) near identifier '$pos' at /usr
/local/systemtap/share/systemtap/tapset/vfs.stp:775:8
WARNING: Number of errors: 1, skipped probes: 2
RC 0
PASS: systemtap.examples/io/traceio run

Ignoring the server and syscall tests, that leaves us with the following
34 FAILs:

FAIL: backtrace (1 0)
FAIL: backtrace-unwindsyms (1 0)

Fails everywhere.

FAIL: ./bz5274 longjmp to a uretprobed function
FAIL: cmd_parse1: unexpected EOF
FAIL: labels exe .label
FAIL: OVERLOAD1 startup (eof)
FAIL: OVERLOAD2 startup (eof)
FAIL: OVERLOAD3 startup (eof)

Not analysed.

FAIL: sdt ""
FAIL: sdt additional_flags=-std=gnu89
FAIL: sdt c++ additional_flags=-std=gnu89
FAIL: sdt 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="-O3"

Seems none of the probes ever get hit, they all fail with:
too few lines of output, got 0, expected 10

FAIL: skip tracking (timeout)
FAIL: skip tracking (2 0)
FAIL: static_uprobes C (0)
FAIL: systemtap.base/stmt_rel.stp
FAIL: uprobes -p5 (0)
FAIL: systemtap.base/uprobes_lib.stp
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: int64 function arguments
FAIL: buildok/seventeen.stp
FAIL: Hello from server
FAIL: systemtap.stress/current.stp startup (timeout)



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]