Initial stap support for inode-based uprobes
Mark Wielaard
mjw@redhat.com
Thu Nov 17 09:28:00 GMT 2011
On Wed, 2011-11-16 at 11:39 -0600, David Smith wrote:
> I just got through running the systemtap testsuite on 2 different
> configurations:
>
> 1) stock f16 kernel and HEAD systemtap
>
> # of expected passes 3096
> # of unexpected failures 63
> # of unexpected successes 8
> # of expected failures 259
> # of untested testcases 61
> # of unsupported tests 4
63 FAILs seems a bit high. For comparison these are my results on the
same setup (assuming x86_64, but i686 on f15 is similar, and even on
x86_64/rhel5 I don't get more than 30 FAILs - admittedly I did clean up
the testsuite in the last week, so if your run is from a couple of days
ago then you might want to rerun):
Host: Linux toonder.wildebeest.org 3.1.1-1.fc16.x86_64 #1 SMP Fri Nov 11
21:47:56 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.7/0.152 commit release-1.6-419-g0f7b51d
GCC: 4.6.2 [gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1)]
Distro: Fedora release 16 (Verne)
# of expected passes 3142
# of unexpected failures 20
# of unexpected successes 8
# of expected failures 259
# of untested testcases 62
# of unsupported tests 2
Do you know where those extra 40 FAILs come from?
Below is my FAIL list. 13 come from the nd_syscall testcase, which
probably should be marked KFAIL (or is that XFAIL).
Cheers,
Mark
FAIL: cast-scope
FAIL: buildok/nfs_proc-detailed.stp
FAIL: buildok/nfsd-all-probes.stp
FAIL: buildok/nfsd-detailed.stp
FAIL: buildok/rpc-detailed.stp
FAIL: buildok/vfs-detailed.stp
FAIL: semok/thirtynine.stp
FAIL: 64-bit dup nd_syscall
FAIL: 64-bit eventfd nd_syscall
FAIL: 64-bit inotify nd_syscall
FAIL: 64-bit pipe nd_syscall
FAIL: 64-bit poll nd_syscall
FAIL: 64-bit signalfd nd_syscall
FAIL: 32-bit dup nd_syscall
FAIL: 32-bit eventfd nd_syscall
FAIL: 32-bit inotify nd_syscall
FAIL: 32-bit net1 nd_syscall
FAIL: 32-bit pipe nd_syscall
FAIL: 32-bit poll nd_syscall
FAIL: 32-bit signalfd nd_syscall
More information about the Systemtap
mailing list